On Thu, Mar 24, 2005 at 03:21:08AM +0100, Henk de Bruijn wrote: > On Wed, 23 Mar 2005 15:08:19 -0500GMT (23-3-2005, 21:08 +0100, where I > live), David Shaw wrote: > > > On Wed, Mar 23, 2005 at 09:02:27PM +0100, Henk de Bruijn wrote: > > >> I changed the digest algo from SHA1 to RIPEMD160 > > > This does not tell me anything useful. I don't know what mailer you > > are using, and I don't know how you are calling GnuPG. Specifically, > > and *exactly*, what did you change. Did you stick "digest-algo > > ripemd160" in your gpg.conf? Did you do something in a mailer config > > file? Did you change something on the command line? Did you do > > something else? > > Sorry for not telling relevant information. As you can see in my > signature I am using The Bat! Further I use GnuPG 1.4.1 with GPGShell > 3.40rc2. > In GPGshell under Preferences GnuPG, on the second tab I changed the > digest algo from default to RIPEMD160. > After having kept this change, the gpg.conf has a line: > digest-algo RIPEMD160 > > When I now send messages signed inlined, these messages verify ok but > when I send a message like this one, signed PGP/MIME, I get this error > message.
You get the error when you *send* a message, or when you *verify* a message? What happens if you remove the 'digest-algo RIPEMD160' line from gpg.conf? I see also that you are using The Bat! v3.0.9.9. That version is a pre-beta that came out yesterday. You're not the first person who is reporting this error with The Bat! so I'm wondering if the Bat folks changed something internally. David _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
