[ http://jira.codehaus.org/browse/MGPG-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=221465#action_221465 ]
SebbASF commented on MGPG-17: ----------------------------- Just tried again with gpg (GnuPG) 1.4.10, and it works fine. I think the problem is that gpg2.exe (which may also be installed as gpg.exe) does not handle the passphrase-fd parameter in the same way as earlier versions of gpg. According to http://linux.die.net/man/1/gpg2 The --passphrase-fd option is only used by gpg2 if --batch is also specified. IMO GPG2 really ought to print a warning for this change in behaviour. The --batch option is also valid for earlier versions of gpg, so the solution is to add --batch when providing a password. Since GPG2 cannot get the password from fd0, it will start the gpg-agent which will then cache the password for a while. I think this explains why the prompt sometimes re-appears. A work-round is to ensure that the version of gpg found by Maven is not gpg2, but an earlier version. > password is specified, but still promting > ----------------------------------------- > > Key: MGPG-17 > URL: http://jira.codehaus.org/browse/MGPG-17 > Project: Maven 2.x GPG Plugin > Issue Type: Bug > Affects Versions: 1.0-alpha-4 > Environment: Apache Maven 2.2.0 (r788681; 2009-06-26 08:04:01-0500) > Java version: 1.6.0_15 > Java home: /usr/lib/jvm/java-1.6.0-sun-1.6.0/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.27.29-0.1-default" arch: "i386" Family: "unix" > gpg (GnuPG) 2.0.9 > on OpenSUSE 11.1 > Reporter: Albert Kurucz > > Using > mvn verify -Dgpg.passphrase=thephrase > with thephrase replaced with the real one. > When it get to signing, it still promts. > It is critical, because this prompt repeats with all the 100 modules of the > project. > Problem maybe related to updates/changes of gpg software. > Related warning message: > gpg: WARNING: "--no-use-agent" is an obsolete option - it has no effect > can't connect to `/home/albert_kurucz/.gnupg/S.gpg-agent': No such file or > directory -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
