[pkg-gnupg-maint] Bug#834548: gnupg2: Ignores secret-keyring config when importing secret keys from gpg1
Mike Hommey
mh+reportbug at glandium.org
Tue Aug 16 23:23:13 UTC 2016
Package: gnupg2
Version: 2.1.11-7
Severity: important
Dear Maintainer,
The recent upgrade of gnupg left me with with no usable private keys.
gpg -K would display nothing. (the package version information comes
from a downgrade, don't trust it).
The core problem, as it seems, is that my gpg.conf has a secret-keyring
config item pointing to a file that is not ~/.gnupg/secret.gpg and that
contains my private keys. But gpg2 seems to always want to import
~/.gnupg/secret.gpg, disregarding the config.
So, it would seem the workaround for me is to copy that secret-keyring
to ~/.gnupg/secret.gpg, have gpg2 do its conversion, then move the
private-keys-v1.d directory where the secret-keyring used to be... and
create a symbolic link, since apparently, there's no option like
secret-keyring to point to a different directory...
Mike
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gnupg2 depends on:
ii dpkg 1.18.10
ii gnupg-agent 2.1.11-7
ii install-info 6.1.0.dfsg.1-8
ii libassuan0 2.4.3-1
ii libbz2-1.0 1.0.6-8
ii libc6 2.23-4
ii libgcrypt20 1.7.2-2
ii libgpg-error0 1.24-1
ii libksba8 1.3.4-4
ii libreadline6 6.3-8+b4
ii libsqlite3-0 3.14.1-1
ii zlib1g 1:1.2.8.dfsg-2+b1
Versions of packages gnupg2 recommends:
ii dirmngr 2.1.14-5
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