Mailinglist Archive: opensuse-bugs (4295 mails)

< Previous Next >
[Bug 1040289] gpg2 decrypt fails after update to 2.1.21-1.1
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 23 May 2017 08:10:07 +0000
  • Message-id: <bug-1040289-21960-lVCIQWdcx3@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=1040289
http://bugzilla.suse.com/show_bug.cgi?id=1040289#c2

Petr Cervinka <pcervinka@xxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |pcervinka@xxxxxxxx

--- Comment #2 from Petr Cervinka <pcervinka@xxxxxxxx> ---
I confirm exactly the same behavior on Tumbleweed, gpg fails with "No secret
key" error.
So far, I tested rollback to previous TW snapshot, gpg works fine with previous
version.

I also did a test with backup(used by gpg2-2.0.24-8.1) of ".gnupg" folder.
Latest gpg proceeds with migration, but fails again.

gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/home/petr/.gnupg/secring.gpg' to gpg-agent
gpg: key E1F7622DF4882DD0: secret key imported
gpg: migration succeeded
gpg: encrypted with 2048-bit RSA key, ID 0BA102312BA1C30C, created 2017-05-03
"Petr Cervinka <pcervinka@xxxxxxxx>"
gpg: public key decryption failed: End of file
gpg: decryption failed: No secret key

It doesn't look related to key corruption in version 2.1.20.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References