digest-algo problem with 1.2.3rc2
Tue Aug 5 13:28:01 2003
-----BEGIN PGP SIGNED MESSAGE-----
On Mon, Aug 04, 2003 at 05:58:09PM -1000, Denis McCauley wrote:
> Sorry if I didn't make myself clear. The problem was essentially with
> loading my keyrings (with GPGshell). All I got was a blank frame.
> --list-keys and --list-secret-keys at the command line gave me the error
> message mentioned above, even after I commented out the offending
> "s2k-cipher-algo" option.
> I didn't try --edit-key at that stage. Instead, I changed the private
> keyring for an empty one, my public keys then all listed OK, so I
> reinstated by private keyring. Then I did --edit-key and changed the
> passwords in GPGshell. Somewhat tortuous, but I got there in the end.
> But my point really was that the "read" capability for SHA256 seems to
> have a hole in it, so to speak.
Can you try to duplicate the problem and post the steps you followed?
GnuPG works fine with a s2k digest of sha256. The error message you
got also doesn't follow from the scenario you describe - if a s2k
digest was used that GnuPG can't handle, the error message is
"md_enable: algorithm %d not available".
I'm wondering if you didn't really comment out the s2k-digest-algo
line, which would give you the exact problem you described.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3rc2 (GNU/Linux)
Comment: Key available at http://www.jabberwocky.com/david/keys.asc
-----END PGP SIGNATURE-----