[
https://issues.apache.org/jira/browse/WHIMSY-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881836#comment-16881836
]
Sebb commented on WHIMSY-275:
-----------------------------
AFAICT that key (FADD9AF1C6B413C7) is not present on the keyserver[1], though
it is in the sks-pool.
For keys that are present, e.g. 1D28809A20546256, the version of gpg2 on whimsy
returns an error, but works on my system.
I suspect that is because the version of gpg2 on Whimsy is quite old, rather
than because of an incorrect command line.
BTW, we should probably add --batch to the gpg command qualifiers.
[1] https://keys.openpgp.org/search?q=FADD9AF1C6B413C7
> GPG verification no longer working
> ----------------------------------
>
> Key: WHIMSY-275
> URL: https://issues.apache.org/jira/browse/WHIMSY-275
> Project: Whimsy
> Issue Type: Bug
> Components: SecMail
> Reporter: Matt Sicker
> Assignee: Craig L Russell
> Priority: Major
>
> After changing to keys.openpgp.org, no signatures can be verified in Whimsy.
> Take any of the recent .asc-signed ICLAs in the workbench and they'll all
> fail to verify the public key. If you try downloading those keys directly via
> gpg using keys.openpgp.org (or searching on their site), you'll find the
> appropriate keys, though Whimsy will still give a "no public key" error.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
