gpg 1.9.93 -- wrong use of gpg-agent

Patrick Brunschwig patrick at
Thu Oct 19 09:49:59 CEST 2006

I think there's definitely something wrong with using gpg-agent in gpg2.
It seems that I'm unable to provide the passphrase via --command-fd,
gpg2 always calls the gpg-agent, even if I explicitly disable this.

# gpg2 -v -v --batch --no-use-agent --charset utf8  --no-tty \
--status-fd 1 --logger-fd 1 --command-fd 0 --ask-cert-level \
--edit-key 412D23A373B467E0
gpg: using classic trust model
gpg: key CCEC227B: accepted as trusted key
gpg: key 73B467E0: accepted as trusted key
[GNUPG:] GET_LINE keyedit.prompt
[GNUPG:] USERID_HINT 412D23A373B467E0 enigmail <enigmail at localhost>
[GNUPG:] NEED_PASSPHRASE 412D23A373B467E0 412D23A373B467E0 17 0
gpg: no running gpg-agent - starting one
gpg: DBG: connection to agent established
cant lock memory: Cannot allocate memory
Warning: using insecure memory!
gpg-agent[2954]: command get_passphrase failed: Operation cancelled
gpg: cancelled by user

This is my gpg.conf file (it's also interesting that the
"no-secmem-warning" entry is disregarded):

keyserver  hkp://


More information about the Gnupg-devel mailing list