Why expire?
CL Gilbert
Lamont_Gilbert@RigidSoftware.com
Wed Jul 30 03:58:02 2003
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David Shaw wrote:
|
|
| I think that's a good description. There have been suggestions on
| changing the expiration system to an optional "hard" (non-changeable)
| expiration, as the old PGP 2.x keys had, but this looks like it won't
| be happening soon for a few technical reasons.
|
| David
I agree with that too. In general the less things that are hard, the
less you have to worry about being broken. Who cares if the date has an
error now, its not that big of a deal. but make the date hard, and
someone may decide to base some convoluted security model on it. And
since its supposed to be hard, who can really argue with them?
My favorite part about public key encryption is the 'public' part. The
less that has to be secure the better I think.
_______________________________________________
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
- --
Thank you,
CL Gilbert
"Then said I, Wisdom [is] better than strength: nevertheless the poor
man's wisdom [is] despised, and his words are not heard." Ecclesiastes 9:16
GnuPG Key Fingerprint:
82A6 8893 C2A1 F64E A9AD 19AE 55B2 4CD7 80D2 0A2D
GNU Privacy Guard http://www.gnupg.org
Free interface to Freechess.org
http://www.rigidsoftware.com/Chess/chess.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE/JyaHVbJM14DSCi0RAg2ZAKDYMeU7Zk2XjvLjDpZNCCfqj1gUzACgwbaD
s4sMwn6f4b+j32tkkRuvCss=
=mGSy
-----END PGP SIGNATURE-----