You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whimsical.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2019/07/09 20:11:00 UTC
[jira] [Comment Edited] (WHIMSY-275) GPG verification no longer
working
[ https://issues.apache.org/jira/browse/WHIMSY-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881308#comment-16881308 ]
Sebb edited comment on WHIMSY-275 at 7/9/19 8:10 PM:
-----------------------------------------------------
Example error:
{noformat}
gpg: Signature made Mon Jul 8 09:35:55 2019 UTC
gpg: using RSA key FADD9AF1C6B413C7
gpg: Can't check signature: No public key
gpg: Note: no default option file '/srv/gpg/gpg.conf'
gpg: enabled debug flags: ipc
gpg: DBG: chan_3 <- # Home: /srv/gpg
gpg: DBG: chan_3 <- # Config: [none]
gpg: DBG: chan_3 <- OK Dirmngr 2.1.11 at your service
gpg: DBG: chan_4 <- # Home: /srv/gpg
gpg: DBG: chan_4 <- # Config: [none]
gpg: DBG: chan_4 <- OK Dirmngr 2.1.11 at your service
gpg: DBG: connection to the dirmngr established
gpg: DBG: chan_4 -> GETINFO version
gpg: DBG: chan_4 <- D 2.1.11
gpg: DBG: chan_4 <- OK
gpg: DBG: chan_4 -> KEYSERVER --clear hkp://keys.openpgp.org
gpg: DBG: chan_4 <- OK
gpg: DBG: chan_4 -> KS_GET -- 0xFADD9AF1C6B413C7
gpg: DBG: chan_4 <- S PROGRESS tick ? 0 0
gpg: DBG: chan_4 <- ERR 1 General error <Unspecified source>
gpg: keyserver receive failed: General error
gpg: DBG: chan_4 -> BYE
gpg: secmem usage: 0/65536 bytes in 0 blocks
{noformat}
was (Author: jvz):
Example error:
{noformat}
gpg: Signature made Mon Jul 8 09:35:55 2019 UTC gpg: using RSA key FADD9AF1C6B413C7 gpg: Can't check signature: No public key gpg: Note: no default option file '/srv/gpg/gpg.conf' gpg: enabled debug flags: ipc gpg: DBG: chan_3 <- # Home: /srv/gpg gpg: DBG: chan_3 <- # Config: [none] gpg: DBG: chan_3 <- OK Dirmngr 2.1.11 at your service gpg: DBG: chan_4 <- # Home: /srv/gpg gpg: DBG: chan_4 <- # Config: [none] gpg: DBG: chan_4 <- OK Dirmngr 2.1.11 at your service gpg: DBG: connection to the dirmngr established gpg: DBG: chan_4 -> GETINFO version gpg: DBG: chan_4 <- D 2.1.11 gpg: DBG: chan_4 <- OK gpg: DBG: chan_4 -> KEYSERVER --clear hkp://keys.openpgp.org gpg: DBG: chan_4 <- OK gpg: DBG: chan_4 -> KS_GET -- 0xFADD9AF1C6B413C7 gpg: DBG: chan_4 <- S PROGRESS tick ? 0 0 gpg: DBG: chan_4 <- ERR 1 General error <Unspecified source> gpg: keyserver receive failed: General error gpg: DBG: chan_4 -> BYE gpg: secmem usage: 0/65536 bytes in 0 blocks
{noformat}
> 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)