-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Edwin Woudt wrote:
Jon Callas <jon(_at_)callas(_dot_)org> replied:
I think an S2K that includes a hash is only mildly hackish, myself. I'd
support this. I'd even support an additional one that is merely salted
with a hash.
I disagree. As Werner Koch already pointed out, the 'correct' solution is
to introduce version 5 of the secret key packet. I however do not think
that there is any real reason for introducing a v5 public key packet, given
that nothing changed for public key packets.
Keeping v4 public key packets will make sure nothing is broken with regard
to exchanging public keys. Exchanging secret keys with older
implementations will be broken in both cases anyway, because of the new s2k
type.
Edwin
v5 seckey packet will broke seckey exchange with older versions,
while new s2k not - it will still be possible to import seckey in older ver
with aged workaround - unprotect them, export, import into older ver, protect
again.
== <EOF> ==
Disastry http://i.am/disastry/
http://disastry.dhs.org/pgp <----PGP plugins for Netscape and MDaemon
^--GPG for Win32 (supports loadable modules and IDEA)
^---PGP 2.6.3ia-multi04 (supports IDEA, CAST5, BLOWFISH, TWOFISH,
AES, 3DES ciphers and MD5, SHA1, RIPEMD160 hashes)
-----BEGIN PGP SIGNATURE-----
Version: Netscape PGP half-Plugin 0.14 by Disastry / PGPsdk v1.7.1
iQA/AwUBO4ZntDBaTVEuJQxkEQMjSACg7AnKTW18uAAmrmiAqwysCU4WKkoAoNHq
Cl75N3ysOGDYGqp5In6YJpbZ
=/i+s
-----END PGP SIGNATURE-----