Package: gnupg-agent Version: 2.1.7-2 $ gpg-connect-agent --no-autostart -- NOP /bye gpg-connect-agent: no gpg-agent running in this session $ echo $? 0 $
The exit status should indicate an error if the connection fails, as it did before GnuPG 2.1. (My shell startup script runs gpg-agent for its ssh support, when not already running, and this change breaks it.) A workaround is to avoid --no-autostart, and pass a bad --agent-program: $ gpg-connect-agent --agent-program /dev/null -- NOP /bye gpg-connect-agent: no running gpg-agent - starting '/dev/null' gpg-connect-agent: failed to start agent '/dev/null': Permission denied gpg-connect-agent: can't connect to the agent: Permission denied gpg-connect-agent: error sending standard options: No agent running $ echo $? 1 $ - Michael -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: arm64 Kernel: Linux 4.1.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages gnupg-agent depends on: ii libassuan0 2.2.1-1 ii libc6 2.19-19 ii libgcrypt20 1.6.3-2 ii libgpg-error0 1.19-2 ii libnpth0 1.2-1 ii libreadline6 6.3-8+b3 ii pinentry-curses [pinentry] 0.9.5-4 ii pinentry-qt4 [pinentry] 0.9.5-4 Versions of packages gnupg-agent recommends: ii gnupg 1.4.19-5 ii gnupg2 2.1.7-2 gnupg-agent suggests no packages. -- no debconf information
signature.asc
Description: Digital signature