From: "Iñigo Serna" <inigoserna@gmail.com>
To: Daiki Ueno <ueno@gnu.org>
Cc: 22941@debbugs.gnu.org
Subject: bug#22941: 25.1.50; epa-list-secret-keys does not find gpg private keys
Date: Fri, 11 Mar 2016 18:17:24 +0100 [thread overview]
Message-ID: <8737rxdjdn.fsf@gmail.com> (raw)
In-Reply-To: <m3ziu79fh1.fsf-ueno@gnu.org>
Hello, and thanks for your answer.
Daiki Ueno <ueno@gnu.org> writes:
> [...]
>
> This behavior is intended, if the key was created with gpg2. GnuPG 2.1
> removed support for secring.gpg, which was used by pre-2.1 versions.
> That is one of the reasons we switched the default to "gpg2".
Sorry, I don't understand.
The key was generated with gpg v1.x, and I want to continue using gpg
v1.x within emacs. From cli, I can see the correct key with "gpg -K".
I understand from the doc you cited that now it is not possible
to use gpg v1.x keys with gpg v2.1+ and vice versa. But in my case I
want to use a v1.x key with gpg v1.x. And that's why I set
`epg-pgp-program' to "gpg" instead of using default "gpg2".
Am I missing something?
Thanks in advance,
Iñigo Serna
> tag 22941 notabug
> close 22941
> stop
>
> Iñigo Serna <inigoserna@gmail.com> writes:
>
>> Since a couple of months ago emacs 25.0.x (last tested as 2016/03/08
>> from git master) can't open encrypted files (using symmetric keys), as
>> epa can't find secret keys from gpg.
>>
>> This is the error message I get:
>> """
>> Error while decrypting with "gpg":
>>
>> gpg: encrypted with 2048-bit RSA key, ID C0ED9C8489B28C43, created 2016-01-12
>> "Iñigo Serna (XXX.YY) <inigo@XXX.YY>"
>> gpg: decryption failed: No secret key
>> """
>>
>> I use gpg (not gpg2) so I added '(setq epg-gpg-program "gpg")' to my
>> configuration as new epa defaults to gpg2 when I've run "emacs -Q -nw".
>>
>> `epa-list-secret-keys` does not find any keys.
>>
>> This same configuration works ok with 24.5.1 (from Fedora 23 x86_64), and
>> even `epa-list-secret-keys` shows the private keys correctly.
>
> This behavior is intended, if the key was created with gpg2. GnuPG 2.1
> removed support for secring.gpg, which was used by pre-2.1 versions.
> That is one of the reasons we switched the default to "gpg2".
>
> See doc/whats-new-in-2.1.txt in GnuPG:
>
> 1.1 Removal of the secret keyring
> ─────────────────────────────────
> [...]
> 2.1. However, any change to the private keys using the new /gpg/ will
> not show up when using pre-2.1 versions of GnuPG and vice versa.
>
> Regards,
--
Iñigo Serna
next prev parent reply other threads:[~2016-03-11 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 10:58 bug#22941: 25.1.50; epa-list-secret-keys does not find gpg private keys Iñigo Serna
2016-03-10 3:30 ` Daiki Ueno
2016-03-11 17:17 ` Iñigo Serna [this message]
2016-03-11 22:23 ` Daiki Ueno
2016-03-12 11:06 ` Iñigo Serna
2016-03-14 6:01 ` Daiki Ueno
2016-03-14 9:13 ` Iñigo Serna
2016-03-14 9:26 ` Daiki Ueno
2016-03-14 10:02 ` Iñigo Serna
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737rxdjdn.fsf@gmail.com \
--to=inigoserna@gmail.com \
--cc=22941@debbugs.gnu.org \
--cc=ueno@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.