Bug#412993: gnupg-agent: Xsession.d/90gpg-agent should start agent unconditionally

2012-01-26 Thread Andre Heinecke
regardless of alternatives that are available: - Current gnupg Versions rely on gpg-agent, - gpg-agent should be started as a daemon or otherwise it does not need to be installed at all. - The configuration option that debian relies on is deprecated. - A user of Kleopatra for example without

Bug#412993: gnupg-agent: Xsession.d/90gpg-agent should start agent unconditionally

2011-09-30 Thread Ludwig Reiter
We run into this issue again. Version Debian/Squeeze 2.0.14. The option use-agent is deprecated in the conf, so why should a user has it in his gpg-conf. See manual page of gpg2: --use-agent --no-use-agent This is dummy option. gpg2 always requires the agent. So the

Bug#412993: gnupg-agent: Xsession.d/90gpg-agent should start agent unconditionally

2007-05-18 Thread Edward Guldemond
I think that searching the GnuPG options file is wrong. Could the script instead look for use-gpg-agent in /etc/X11/Xsession instead? This is the same mechanism that the SSH agent uses to determine if it should start up when X is started. -- Ed signature.asc Description: Digital signature

Bug#412993: gnupg-agent: Xsession.d/90gpg-agent should start agent unconditionally

2007-03-01 Thread Bernhard Herzog
Package: gnupg-agent Version: 2.0.2 Severity: normal The gpg-agent package installs /etc/X11/Xsession.d/90gpg-agent to automatically start the agent in X sessions. The script tries to determine whether the agent is needed by looking for the use-agent option in some gnugp configuration files.