Question to WKD-Feature

Bernhard Reiter bernhard at
Mon Nov 7 09:14:57 CET 2016


[WKD https get method must return the binary representation]

Am Freitag, 4. November 2016, 21:03:37 schrieb Werner Koch:
> It is binary because HTTP transports binary data just fine.
> In contrast SMTP is not able to transport binary

what do you think about the idea to also allow "ascii armored"
so that some server implementations (of WKS) could manage the pubkeys
without looking into the contents? They could just deliver the ascii 
armored pubkey they've gotten from the client via auth-summit.

Best Regards,

-- (CEO) (Founding GA Member)
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20161107/5216a225/attachment.sig>

More information about the Gnupg-devel mailing list