[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Encoding "secret key is hashed"
-----BEGIN PGP SIGNED MESSAGE-----
"Edwin Woudt" <edwin@xxxxxxxx> wrote:
> I assume that you still want to change the version number to 5 as in your
> March posting?
No, I don't want both changes. Originally, I liked a version
change, but I've been convinced that its implications are a mess.
It seemed that others were uncomfortable with having the the public
and secret key versions out of sync, and I can appreciate that. The
version number is included in the hashes for fingerprints and for
signatures, so one would either have to map "secret version 5" to
"public version 4", or include the public-key version number in the
secret-key packet. The latter is cleaner, but it still may be
a little disruptive.
So, Hal Finney's suggestion (change the pre-S2K byte) sounded like
a fair alternative, as it wouldn't require changing the version number,
but it also doesn't disrupt the S2K (which is used elsewhere).
By the way, this hash would include *all* the key material, including
the public part, right?
-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Privacy 6.5.3
-----END PGP SIGNATURE-----