[Pkg-gnupg-maint] Bug#760644: gnupg2: Difficult to import stub secret keys with existing ones present
Mark Brown
broonie at debian.org
Sat Sep 6 12:32:58 UTC 2014
Package: gnupg2
Version: 2.0.26-2
Severity: normal
The standard way to create stub secret keys for smartcards is to use
gpg2 --card-status. Sadly if there are existing stub keys (for example,
when using multiple cards) this operation appears to have no effect and
not import secret keys. It is possible to work around this by shuffling
secret keys around by hand but it isn't a good user experience.
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gnupg2 depends on:
ii dpkg 1.17.13
ii gnupg-agent 2.0.26-2
ii install-info 5.2.0.dfsg.1-4
ii libassuan0 2.1.2-2
ii libbz2-1.0 1.0.6-7
ii libc6 2.19-10
ii libcurl3-gnutls 7.37.1-1
ii libgcrypt20 1.6.2-3
ii libgpg-error0 1.13-4
ii libksba8 1.3.0-3
ii libreadline6 6.3-8
ii zlib1g 1:1.2.8.dfsg-2
Versions of packages gnupg2 recommends:
ii libldap-2.4-2 2.4.39-1.1+b1
Versions of packages gnupg2 suggests:
pn gnupg-doc <none>
pn parcimonie <none>
pn xloadimage <none>
-- no debconf information
More information about the Pkg-gnupg-maint
mailing list