[
https://issues.apache.org/jira/browse/MGPG-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated MGPG-92:
-----------------------------
Description: 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 "extra" gpg-agent socket. We had to "upgrade" to using the
"standard" socket, which probably exposes more gpg features to the isolated
environment than we would like. (was: 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.)
> `--pinentry-mode error` cannot be used with gpg-agent "extra" 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
> "extra" gpg-agent socket. We had to "upgrade" to using the "standard" 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)
