[jira] Updated: (INFRA-1195) gpg signing broken on people.apache.org

["Justin Mason (JIRA)" <ji...@apache.org>]

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

Justin Mason updated INFRA-1195:
--------------------------------

    Summary: gpg signing broken on people.apache.org  (was: gpg broken on people.apache.org)

(hmm. updated summary line; it's probably not all use of gpg that's broken, but signing certainly is)

> 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 <re...@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.