Page MenuHome GnuPG

gpg --quiet doesn't suppress messages "requesting key XXX ..." / noise on STDERR/STDOUT
Closed, ResolvedPublic


A Debian user complained, that `gpg --quiet --refresh-keys' is not very quiet.
I'm wondering if line 1155 in g10/keyserver.c should consider opt.quiet too?


External Link

Event Timeline

dleidert set External Link to
dleidert added a subscriber: dleidert.

Another user reported in this (I can verify it):

During a full refresh of the keyring, gpg seems to output all information
to STDERR and STDOUT. This makes it inconvenient to have a cron job to refresh
keys, because it can result in a very large and fairly useless mail.

Please ensure that normal output goes to STDOUT and errors and warnings to
STDERR so that problems aren't lost in the noise from this command.

Indeed some "normal" messages go to stderr and some warnings go to stdout.

dleidert renamed this task from gpg --quiet doesn't suppress messages "requesting key XXX ..." to gpg --quiet doesn't suppress messages "requesting key XXX ..." / noise on STDERR/STDOUT.Jul 17 2012, 8:26 PM

I need to verify this. It is possible that we do a keylisting while importing
keys and the keylisting prints to stdout. If that is the case, we can't change
it because gpgme and scripts may reply on it.

Using --quiet for --refresh-keys makse sens, though.

werner claimed this task.

In 2.1 --quit is honored here