On Thu, Aug 23, 2018 at 12:54 PM Martin T wrote:
>
> Hi!
>
> I reinstalled my workstation and moved ~/.gnupg directory from old
> machine to new one. Gpg version in both workstations is 2.1.18. The
> problem is, that in the new workstation, when I try to decrypt a file,
> it doesn't find the secre
Hi!
I reinstalled my workstation and moved ~/.gnupg directory from old
machine to new one. Gpg version in both workstations is 2.1.18. The
problem is, that in the new workstation, when I try to decrypt a file,
it doesn't find the secret key:
$ gpg -o .file -d .file.gpg
gpg: encrypted with RSA key
Hi,
On 08/23/2018 10:54 AM, Martin T wrote:
> When I start the "gpg --list-secret-keys" with "strace -e open",
> then ~/.gnupg/secring.gpg file is not searched.
GnuPG >= 2.1 does not use ~/.gnupg/secring.gpg anymore. Secret keys are
now stored in the ~/.gnupg/private-keys-v1.d folder (one file pe
On Thu, 23 Aug 2018 17:50, gnupg-users@gnupg.org said:
> Related question: Do you have a file named "gpg-v21-migrated" in your
> .gnupg directory?
The file name is actually ".gpg-v21-migrated" (note the leading dot) and
thus only listed by ls with the option -a.
Shalom-Salam,
Werner
--
Di
Resending with a compressed log file since it ended up way bigger than I
expected.
Forwarded Message
Subject: Re: GPGME status callback not working for need entropy
Date: Thu, 23 Aug 2018 16:54:13 -0400
From: Jacob Adams
To: gnupg-users@gnupg.org
On 08/22/2018 04:38 AM, Werner
Hi!
Thanks for replies! The problem was indeed the existing
~/.gnupg/.gpg-v21-migrated file. Once I removed it, I did see the keys
in the output of "gpg --list-keys" and "gpg --list-secret-keys".
One more small question- in the output of "gpg --list-keys" or "gpg
--list-secret-keys" I see two key
