David Shaw wrote: > Ah, I recall this problem. I reported it to the PGP GD people quite a > while ago, and I thought it had been fixed. The GD was generating a > PGP/MIME micalg setting of pgp-sha1, but the actual signature was > being made with SHA256.
Found it. That's exactly what's happening and obviously the problem still hasn't been fixed (or else it raised its ugly head again). ===== Content-type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary=PGP_Universal_2F4EB16A_4F41CA65_EABA882D_FCFE19A6 ===== Thanks to you both! -- Jim _______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
