GnuPG 1.3.4 SHA256 problem?
jvender at owensboro.net
Tue Dec 2 18:46:18 CET 2003
-----BEGIN PGP SIGNED MESSAGE-----
|> When using the SHA256 hash with the DSA key, I was prompted for
|> a passphrase, which led me to believe that the settings would
|> work, and the partial output was confusing, since I wasn't aware
|> that it wouldn't work. When the SHA256 hash is released
|> (read/write) as part of the next production stable gnupg, new
|> gpg users will probably make the same mistake trying to use
|> SHA256 with a DSA key.
| I'm not sure I get this. You tried something that is impossible, and
| you got an error message ("DSA requires the use of a 160 bit hash
| algorithm") saying so. Where's the problem?
The problem isn't that I got an error message because I did something
that is impossible. It's that gpg created partial, incomplete output
when it was asked to do something that is impossible. gpg output the
following when trying to clearsign the word 'test'
- -----BEGIN PGP SIGNED MESSAGE-----
and then failed, when it would make more sense for it to not create any
output, but instead, just fail if it is asked to do something
impossible. The processing made it through the creation of the message
header and the text that was to be signed before failing. This is what I
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the Gnupg-devel