[#MGPG-17] password is specified, but still promting - jira.codehaus.org

Maven 2.x GPG Plugin

password is specified, but still promting

Created: 05/Sep/09 02:09 AM Updated: 28/Feb/10 02:59 PM

Component/s:

None

Affects Version/s:

1.0-alpha-4

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

« Hide

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

Description

« Hide

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

Sort Order:

[ Permalink | « Hide ]

Albert Kurucz added a comment - 05/Sep/09 02:31 AM

Found this:
http://www.nabble.com/-Bug-53196--NEW:-openpgp-encryption-decryption-not-working:-gpg-agent-not-started-by-default-td25153797.html

after executing this:

gpg-agent --use-standard-socket --daemon 2>/dev/null

password is not prompted any more, just once. strange!

[ Permalink | « Hide ]

Brett Porter added a comment - 05/Sep/09 09:15 AM

so you've established this was a bug on your installation?

[ Permalink | « Hide ]

Eric Chatellier added a comment - 28/Jan/10 09:28 AM

Same problem here.

Maven 2.2.1 with gnupg 2.0.11 on gentoo x86_64.

Password is asked once.

[ Permalink | « Hide ]

Fabrizio Giudici added a comment - 28/Feb/10 02:59 PM

My problem is similar, in a batch environment, but it's intermittent. Sometimes it takes the password specified by the property, other times it fails about not being able to use /dev/tty (which is obvious, since it's a batch run, but the bug is that it doesn't use the password specified in the property). I'm seeing the "obsolete option" warning too.