Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Jun 2003 02:29:19 +0100
From:      Colin Percival <colin.percival@wadham.ox.ac.uk>
To:        David Schultz <das@FreeBSD.ORG>
Cc:        chat@FreeBSD.ORG
Subject:   Re: Cryptographically enabled ports tree.
Message-ID:  <5.0.2.1.1.20030622022111.02c1cdf8@popserver.sfu.ca>
In-Reply-To: <20030622011818.GA59989@HAL9000.homeunix.com>
References:  <5.0.2.1.1.20030621193449.02c91ce8@popserver.sfu.ca> <5.0.2.1.1.20030621175853.02c92e00@popserver.sfu.ca> <20030621163835.GA18653@tulip.epweb.co.za> <5.0.2.1.1.20030621175853.02c92e00@popserver.sfu.ca> <5.0.2.1.1.20030621193449.02c91ce8@popserver.sfu.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
At 18:18 21/06/2003 -0700, David Schultz wrote:
>We already have MD5 checksums of each port, so all it takes is to
>have so@ sign a MAC for the entire ports tree.

   Yes, I'm sure the security officers would be delighted to login and 
enter a PGP passphrase every time someone commits something to the ports 
tree. ;)

>   Now doing
>something more sophistocated and seamless would be a little bit
>more effort...

   What we need is something integrated into the CVS system which rebuilds 
the necessary signatures every time the ports tree is modified, and commits 
those into the CVS tree.  Any CVS experts around who could say how to do this?

Colin Percival




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.0.2.1.1.20030622022111.02c1cdf8>