Re: Fwd: [PATCH]: gnus: use correct GPG hash algorithm in 'micalg' field

[Daiki Ueno <ueno@unixuser.org>]

Hello,

> Enrico Scholz <enrico.scholz@informatik.tu-chemnitz.de> writes:

> > when creating 'PGP/MIME Sign' signatures with Gnus v5.10.7 (from the
> > xemacs-sumo-20050715 tarball) the Content-Type: will be always something
> > like
> >
> > | Content-Type: multipart/signed; boundary="=-=-=";
> > | 	micalg=pgp-sha1; protocol="application/pgp-signature"
> >                  ~~~~

> The attached patch fixes this; currently, it relies on the special
> status-fd format of gnupg. I do not know if this is standardized
> across all pgp implementations (are there other ones in use with
> gnus?). The new method 'ensc/mml2015-pgg-signinfo' should be moved
> into pgg.el, but I do not have the overview about the gnus/pgg design
> to touch two packages.

I'm not sure that the micalg= parameter is still mandatory, while the
hash algorithm used is embedded in OpenPGP packets.  It can be obtained
by using the builtin packet parser (pgg-parse), without depending on
--status-fd output of GnuPG.

Try the following:

(require 'pgg-parse)

(setq pgg-parse-hash-algorithm-alist
      (nconc pgg-parse-hash-algorithm-alist
	     '((8 . SHA256) (9 . SHA384) (10 . SHA512))))
      
(pgg-parse-armor "\
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iQEVAwUAQuO4ZzyfXseeoEz2AQoJMggArcGx8nhA21/J5QSaiWKC7FzzB2DLSMiq
D4FQD26NEW38CjcBBq9TqTHm8yCI5dOsTjoiMVfhooBMKTel4P0yAhiuqXthx1Im
J7LCIyVtEGJcBeOioN4c/wu0yHUsDM+E4Xuso56M2PpBGOekWO65fmEPRLFULP6b
mreYBrPqApD49Ow7x2qa65Jy1hhSA0tcXYaqW7IfNciUjVLmsV+e4JrJYXQfwD86
wI2A0/WoxQAD8VMH81MUggclmm41drddz3ceSA3PlRHcFL0vQ1/mCHXJ+o5BwuvW
gA4a+S5wTg51RZ/tAfbeIQEkB7sxmjMDLLdCxA26zptt5YILMvNkuQ==
=Et6W
-----END PGP SIGNATURE-----")

=> ((2 (version . 3) (signature-type . "Signature of a binary document")
    (creation-time 17123 47207 0) (key-identifier . "3C9F5EC79EA04CF6")
    (public-key-algorithm . RSA) (hash-algorithm . SHA512)))

Regards,
-- 
Daiki Ueno