[
https://issues.apache.org/jira/browse/MGPG-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821594#comment-17821594
]
Nick Dimiduk commented on MGPG-92:
----------------------------------
I think that I filed this backwards. The extra socket has restricted
permissions, and setting pinentry-mode is not permitted when connecting via the
extra socket.
> `--pinentry-mode error` cannot be used with gpg-agent "standard" socket
> -----------------------------------------------------------------------
>
> Key: MGPG-92
> URL: https://issues.apache.org/jira/browse/MGPG-92
> Project: Maven GPG Plugin
> Issue Type: Bug
> Reporter: Nick Dimiduk
> Priority: Major
>
> Over on HBASE-27312, we found an issue in our release automation, which
> relies on using this plugin and a GnuPG agent for performing builds inside of
> an isolated environment. With GPG version >= 2.1, the plugin will make use of
> {{--pinentry-mode error}}. This feature appears to not be available using the
> "standard" gpg-agent socket. We had to "upgrade" to using the "extra" socket,
> which probably exposes more gpg features to the isolated environment than we
> would like.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
