www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Mason (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-1195) gpg signing broken on people.apache.org
Date Fri, 16 Mar 2007 19:26:09 GMT

    [ https://issues.apache.org/jira/browse/INFRA-1195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481737

Justin Mason commented on INFRA-1195:

ick.  I see your point, but this'll require a rewrite of our release process.  no fun :(

(in the meantime, I've compiled a copy of gnupg 1.4.7 in my ~)

> gpg signing broken on people.apache.org
> ---------------------------------------
>                 Key: INFRA-1195
>                 URL: https://issues.apache.org/jira/browse/INFRA-1195
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>            Reporter: Justin Mason
> gpg --homedir /home/jm/sabuildtools/sasigningkey -bsa Mail-SpamAssassin-3.2.0-pre3.tar.bz2
> gpg: WARNING: unsafe permissions on homedir `/home/jm/sabuildtools/sasigningkey'
> You need a passphrase to unlock the secret key for
> user: "SpamAssassin Signing Key <release@spamassassin.org>"
> 1024-bit DSA key, ID 265FA05B, created 2003-06-09
> gpg-agent[18148]: can't connect server: `ERR 67109133 can't exec `/usr/local/bin/pinentry':
No such file or directory'
> gpg-agent[18148]: can't connect to the PIN entry module: IPC connect call failed
> gpg-agent[18148]: command get_passphrase failed: No pinentry
> gpg: problem with the agent: No pinentry
> gpg: no default secret key: General error
> gpg: signing failed: General error
> You can also demo this by running:
>   echo > tst
>   gpg -bsa tst
> This used to work; looks like someone modifed the gpg binary in /usr/local/bin/gpg  
  on March 5th, presumably via an upgrade.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message