From: Leo Famulari <leo@famulari.name>
To: Sergiu Ivanov <sivanov@colimite.fr>
Cc: help-guix@gnu.org
Subject: Re: gnupg 2.2.29 -> 2.2.30 breaks symmetric decryption (and gpg-agent?)
Date: Sun, 26 Dec 2021 17:45:23 -0500 [thread overview]
Message-ID: <Ycjwg0VWuMCeavnn@jasmine.lan> (raw)
In-Reply-To: <874k6v1kp0.fsf@colimite.fr>
On Sun, Dec 26, 2021 at 02:31:01PM +0100, Sergiu Ivanov wrote:
> Hi,
>
> I have just upgraded my Guix home on a Guix System, which took gnupg
> from 2.2.29 to 2.2.30. When I run gpg -v --decrypt on a file with
> symmetric encryption, I get the following error:
>
> scolobb@quark ~/tmp$ gpg -v --decrypt world.gpg
> gpg: AES.CFB encrypted data
> gpg: no running gpg-agent - starting '/gnu/store/0snfzd41n430ddpq316j9v2z5fn2y62m-gnupg-2.2.30/bin/gpg-agent'
> gpg: waiting for the agent to come up ... (5s)
> gpg: connection to agent established
> gpg: pinentry launched (3287 gtk2 1.1.1 /dev/pts/0 eterm-color :0 20620/1000/996 1000/998 1)
> gpg: problem with the agent: End of file
> gpg: encrypted with 1 passphrase
> gpg: decryption failed: No secret key
[...]
> Does anyone experience similar issues?
Yes, you're describing bug #52483, "GnuPG 2.2.30 cannot do symmetric
encryption":
https://issues.guix.gnu.org/52483
I just pushed commit d03aa942def0037cb32ff1d0cc2ac5d13f1a63df, which
allows you to upgrade your gnupg package to 2.2.32, which fixes this
bug.
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=d03aa942def0037cb32ff1d0cc2ac5d13f1a63df
next prev parent reply other threads:[~2021-12-26 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-26 13:31 gnupg 2.2.29 -> 2.2.30 breaks symmetric decryption (and gpg-agent?) Sergiu Ivanov
2021-12-26 22:45 ` Leo Famulari [this message]
2021-12-27 11:36 ` Sergiu Ivanov
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Ycjwg0VWuMCeavnn@jasmine.lan \
--to=leo@famulari.name \
--cc=help-guix@gnu.org \
--cc=sivanov@colimite.fr \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).