[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Key 69096DFDD7028BEDACC5884BC5E051C79C0BECDB "Key has been compromis
|
From: |
Leo Famulari |
|
Subject: |
Re: Key 69096DFDD7028BEDACC5884BC5E051C79C0BECDB "Key has been compromised" |
|
Date: |
Mon, 27 Feb 2017 18:41:48 -0500 |
|
User-agent: |
Mutt/1.7.2 (2016-11-26) |
On Mon, Feb 27, 2017 at 06:25:42PM -0500, Leo Famulari wrote:
> In a message on February 3 you said, "Can I regenerate a pgp key? I
> think my keys where in the gnome keyring or something, backing up
> ~/.gnupg/secring.pgp didn't keep my keys :/" [0]
Also, I'm not sure which version of GnuPG you were using, but the 2.1
series does not use '$GNUPGHOME/secring.gpg'. It uses
'$GNUPGHOME/private-keys-v1.d' [0].
So, you could lose your private key if you updated from an earlier
series and then tried to migrate your installation by coping
secring.gpg.
[0]
https://www.gnupg.org/documentation/manuals/gnupg/GPG-Configuration.html#index-secring_002egpg-506
https://www.gnupg.org/documentation/manuals/gnupg/GPG-Configuration-Options.html#index-secret_002dkeyring-304