[jira] [Comment Edited] (MGPG-92) `--pinentry-mode error` cannot be used with gpg-agent "extra" socket

["Tamas Cservenak (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MGPG-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17823306#comment-17823306 ] 

Tamas Cservenak edited comment on MGPG-92 at 3/4/24 7:32 PM:
-------------------------------------------------------------

In isolated environment the "bc" signer (see MGPG-105) is recommended, without hoops and loops (and provide key and passphrase as env values).


was (Author: cstamas):
In isolated environment the "bc" signer is recommended, without hoops and loops (and provide key and passphrase as env values).

> `--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)