Summary: | app-crypt/gnupg-2.1.15: gpg: Decryption failed: No secret key | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fernando Rodriguez <frodriguez.developer> |
Component: | New packages | Assignee: | Kristian Fiskerstrand (RETIRED) <k_f> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | crypto+disabled, frodriguez.developer |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 552936 | ||
Attachments: | emerge --info |
Description
Fernando Rodriguez
2016-10-17 20:35:57 UTC
Created attachment 450594 [details]
emerge --info
(In reply to Fernando Rodriguez from comment #0) > I have an alternate keyring that I access as follows: > > 15 gpg --no-default-keyring \ > 16 --keyring=path_to_keyring \ > 17 --secret-keyring=path_to_secret_keyring \ > 18 --trustdb-name=path_to_trustdb $@ > > After a recent update to gnupg-2.1.15 trying to decrypt with it gives: > > gpg: Decryption failed: No secret key secret-keyring has been deprecated for a while and is ignored in 2.1. If you want a separate secret keyring, use a separate homedir and do a gpg --homedir path/to/homedir --import name-of-secring.gpg
>
>
> Also, if I understand correctly, 2.0 is the stable branch upstream [1]. So
> is there a reason for pushing 2.1 to stable users?
2.0 is EOL 2017. 2.1 is also a stable version (called "modern" for disambiguity reasons) and recommended for most users. From announcements: GnuPG "modern" (2.1) comes with the latest features
and is suggested for most users.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|