Setting up wks/ error parsing submission email

[Daniel Kahn Gillmor]

On Thu 2018-12-20 16:47:46 -0500, Fabian A. Santiago wrote:
> root at deviltracks:~# gpg --output clear_snippet.txt --decrypt  pgp_snippet.txt
> gpg: encrypted with 3072-bit RSA key, ID FAD6496868B818DD, created 2018-12-14
>        "test123 <test123 at deviltracks.net>"
>
> and the clear text is:
>
> root at deviltracks:~# cat clear_snippet.txt
> type: confirmation-request
> sender: key-submission at deviltracks.net
> address: test123 at deviltracks.net
> fingerprint: 89CFCD21743DBDD5EB5ABC973879E79EC3420092
> nonce: <redacted>

OK, so gpg is working fine, and the relevant secret key is available.
that's good!

But (i think) it narrows down the problem to your implemetation of
gpg-wks-client.

Perhaps Werner or someone more well-versed in WKD can weigh in here?
Without access to an environment to replicate the problem, i'm at a bit
of a dead end.

   --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20181220/8cc5edd6/attachment.sig>