[Bug 1565963] Re: gpg secret keys not migrated after upgrade to gnupg 2.1

Daniel Kahn Gillmor dkg at fifthhorseman.net
Sat Apr 9 20:57:36 CEST 2016

On Sat 2016-04-09 05:53:36 -0400, Werner Koch <wk at gnupg.org> wrote:
> On Sat,  9 Apr 2016 01:37, dkg at fifthhorseman.net said:
>> It's a little unusual to have ~/.gnupg/private-keys-v1.d not be u+x, as
>> that would imply that the directory isn't listable.  This is probably
>> causing problems for the gpg-agent.
> Yes, gpg-agent provide commands to list private keys and we may
> eventually use that feature to speed up the --list-secret-keys command
> in certain cases.

Makes sense.  At any rate, the lack of u+x appears to make gpg-agent
fail to do the initial key import.

>> I have no idea how this directory got the u+x bit cleared, but maybe
>> that's something that either:
>>  a) gpg-agent could clean up on its own, or
> That is a good idea.  ~/.gnupg is anyway a property of GnuPG and thus
> gpg-agent should be allowed to change the permissions.

Shall i open an issue in https://bugs.gnupg.org/ about this?


More information about the Gnupg-devel mailing list