Quieten gpg-agent output?

Chris Poole lists at chrispoole.com
Thu Dec 15 18:47:46 CET 2011


I start gpg-agent with the -q option to make it quiet.

I then run a script that executes gpg -qse ... on several files,
encrypting and signing them (quietly).

I still find output like this in my terminal window:

> You need a passphrase to unlock the secret key for
> user: "Chris Poole <chris at chrispoole.com>"2048-bit DSA key, ID 7ED39159, created 2010-12-11 (main key ID BAD248F9)

I assume that gpg is reporting this, and then it checks for a key held
by the agent, which it uses (everything works fine, it's just the
output that annoys me).

I could quiten gpg totally, by running gpg ... 2>&1 >/dev/null, but
then I'd also stop any genuine errors that gpg reports. (I run this
command manually, usually, so would see errors.)

Is there a better way to get rid of these "errors"?


More information about the Gnupg-users mailing list