| 1 |
On Sun, Nov 07, 2004 at 04:44:32PM +0100 or thereabouts, Peter Simons wrote: |
| 2 |
> I think it is important to stress that everybody is on the |
| 3 |
> same side here. The important thing right now is how to |
| 4 |
> _fix_ this problem. As I see it, the simplest possible |
| 5 |
> solution is this: |
| 6 |
> |
| 7 |
> (1) Run "find /usr/portage -type f | xargs sha1sum -b" on |
| 8 |
> the Gentoo main system. |
| 9 |
> |
| 10 |
> (2) Sign the output with GPG. |
| 11 |
> |
| 12 |
> (3) Put it into the portage tree. |
| 13 |
> |
| 14 |
> (4) If the user has GPG installed and has manually put the |
| 15 |
> appropriate public key in some place _outside_ of the |
| 16 |
> portage tree, have "emerge sync" verify that the |
| 17 |
> signature is intact and all hashes hold. |
| 18 |
> |
| 19 |
> Done. |
| 20 |
|
| 21 |
|
| 22 |
People place way to much reliance on GPG and other public/private key |
| 23 |
systems... |
| 24 |
|
| 25 |
Let's assume we implement the above steps. What does that buy you? How do |
| 26 |
you know how many people have a copy of the private key used to sign that |
| 27 |
data? How do you know what sort of passphrase is used on it? (or if it |
| 28 |
even has a passphrase) How do you know the box that holds the private key |
| 29 |
is secure? |
| 30 |
|
| 31 |
Most importantly, how do you know when to stop? At some point, you're |
| 32 |
going to have to accept some level of risk. |
| 33 |
|
| 34 |
--kurt |
Archives