how to suppress warning about gpg-agent?
powerman at powerman.name
Mon Mar 8 01:43:17 CET 2010
Looks like we need an option to suppress warning about gpg-agent.
> Long story:
I've a lot of projects (each has separate user account) which use gpg for
encrypting daily backups (from cron) in this way:
gpg --batch --cipher-algo AES256 -c --passphrase-file PASSFILE BACKUP.tar
The problem is, after switching to gpg2 I start receiving a lot of emails
every day with same warning:
"can't connect to `/home/USER/.gnupg/S.gpg-agent': No such file or directory"
I don't like to redirect STDERR output of gpg to /dev/null because I wanna
receive emails in case of problems with backup process. But I don't wanna
receive dozens of useless emails with this warning every day.
I don't like to run gpg-agent as a daemon on all these user accounts just
to suppress this warning message (and there may be additional issues to
make it accessible from cron scripts, too).
I can try to run gpg-agent from same cron script just before using gpg,
and then kill gpg-agent, but this may lead to race conditions in case
gpg-agent already started by that user for other needs.
Looks like there only two real solutions: implement pipe filter for gpg's
STDERR to strip just this message (ugly), and patch gpg to add an option
to suppress this warning.
P.S. I use Gentoo Linux and app-crypt/gnupg-2.0.14.
More information about the Gnupg-users