projects / gnupg2.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 0ce5dbb) | patch
gpg: Accept also armored data from the WKD.
authorWerner Koch <wk@gnupg.org>
Thu, 11 Apr 2019 07:54:28 +0000 (09:54 +0200)
committerDaniel Kahn Gillmor <dkg@fifthhorseman.net>
Fri, 1 Jul 2022 16:06:43 +0000 (17:06 +0100)
commit719945c05bd3c2ba19c490bf1341ae24c8b7be77
tree26973256930b1d20832c7d53a5b97be408abc8fetree | snapshot
parent0ce5dbb44302377985f5fc0e097be2c790c53645commit | diff
gpg: Accept also armored data from the WKD.

* g10/keyserver.c (keyserver_import_wkd): Clear NO_ARMOR.
--

We may even adjust the specs to allow that.  It should not be a
problem for any OpenPGP implementation because armored keys are very
common and de-armoring code is de-facto a mandatory feature.

Signed-off-by: Werner Koch <wk@gnupg.org>
(cherry picked from commit dc4c7f65e32a0cddc075d06fa0132e099bcb6455)

Gbp-Pq: Topic from-2.2.16
Gbp-Pq: Name gpg-Accept-also-armored-data-from-the-WKD.patch
g10/keyserver.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.