RFC3156: "application/pgp-keys" support enigmail, gnus etc

[Daniel Kahn Gillmor]

Hi Uwe--

On 01/27/2014 04:51 AM, Uwe Brauer wrote:
> Hi according to 
> http://tools.ietf.org/html/rfc3156
> 
> 
> A pgpmime signed message contains lines such as
> 
> Content-Type: multipart/signed; boundary="=-=-=";
> 	micalg=pgp-sha1; protocol="application/pgp-signature"
> 
> While an attached key should look like 
> Content-Type: application/pgp-keys
>    Required parameters: none
>    Optional parameters: none
> 
>    A MIME body part of the content type "application/pgp-keys" contains
>    ASCII-armored transferable Public Key Packets as defined in [1],
>    section 10.1.
> 
> I just implemented such a feature for gnus in Xemacs, but it seems that
> enigmail does not recognise the key! Does anybody know whether other MUA
> support this format?

This seems like a question you'd want to ask the MUAs themselsves.

when you say "enigmail does not recognize the key", how did you test it?

in icedove+enigmail 1.6, if i right-click on an attachment that is of
type application/pgp-keys, i get a menu option "Import OpenPGP Key",
which seems like it does what you would want to do with an e-mailed key.

	--dkg

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1010 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20140127/85619eb4/attachment-0001.sig>