| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Tuesday 23 March 2004 15:32, Toby Dickenson wrote: |
| 5 |
> On Tuesday 23 March 2004 13:12, Paul de Vrieze wrote: |
| 6 |
> |
| 7 |
> <snip alot of good stuff> |
| 8 |
> |
| 9 |
> > - As the checking is done post-rsync there is no problem with |
| 10 |
> > infrequent rsync-ing. |
| 11 |
> |
| 12 |
> Im not sure what infrequent rsyncing problem you are avoiding here, |
| 13 |
> but relying *only* on a post-rsync check seems dangerous. |
| 14 |
|
| 15 |
Basically as the signing key has only a (very) limited lifetime if you |
| 16 |
didn't sync for more than a month the signing key would be invalid so |
| 17 |
the portage tree would be invalidated. Alternatively we could use the |
| 18 |
timestamp of the signature on the devkey-list as reference (instead of |
| 19 |
now) but that would require that the timestamp is accurate. |
| 20 |
|
| 21 |
Another way could involve actually having a user locally sign the |
| 22 |
devkey-list post rsync if the signing key is valid. When checking the |
| 23 |
packages then the local signature of the devkey-list needs to be |
| 24 |
validated. |
| 25 |
|
| 26 |
> |
| 27 |
> We certainly need to be careful about what happens if portage is |
| 28 |
> interrupted before this full check is complete. |
| 29 |
|
| 30 |
Indeed. |
| 31 |
|
| 32 |
Paul |
| 33 |
|
| 34 |
- -- |
| 35 |
Paul de Vrieze |
| 36 |
Gentoo Developer |
| 37 |
Mail: pauldv@g.o |
| 38 |
Homepage: http://www.devrieze.net |
| 39 |
-----BEGIN PGP SIGNATURE----- |
| 40 |
Version: GnuPG v1.2.4 (GNU/Linux) |
| 41 |
|
| 42 |
iD8DBQFAYEx9bKx5DBjWFdsRApoDAKCZGqzXfsAfA0y56evKMS7jI2KLrQCfeUVM |
| 43 |
NpUvy8zBnkZsdKJGKt915bA= |
| 44 |
=W9PJ |
| 45 |
-----END PGP SIGNATURE----- |
| 46 |
|
| 47 |
-- |
| 48 |
gentoo-dev@g.o mailing list |
Archives