Package: pinentry-curses Version: 0.8.3-2 Severity: normal Tags: upstream Dear Maintainer,
When two parallel instance gpg(1) prompt the user for a passphrase,
there should be a locking mechanism to avoid both pinentry to try to
modify the TTY at the same time.
The problem is visible in the following example:
$ killall -u $(whoami) -HUP gpg-agent
$ echo blah | gpg --recipient $keyID --encrypt \
| gpg --use-agent --decrypt | gpg --use-agent --sign >/dev/null
(Another example is where one decrypts a file and sends the cleartext
to a remote machine through SSH, where the SSH key is in fact an OpenPGP
subkey with Authentication capability, which is decrypted using
a ProxyCommand.)
Thanks!
Cheers,
--
Guilhem.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (990, 'unstable'), (800, 'testing'), (700, 'stable'), (1,
'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages pinentry-curses depends on:
ii libc6 2.19-1
ii libncursesw5 5.9+20140118-1
ii libtinfo5 5.9+20140118-1
pinentry-curses recommends no packages.
Versions of packages pinentry-curses suggests:
pn pinentry-doc <none>
-- no debconf information
signature.asc
Description: Digital signature
