On Sat 2016-04-09 05:53:36 -0400, Werner Koch <w...@gnupg.org> wrote: > On Sat, 9 Apr 2016 01:37, d...@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? --dkg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565963 Title: gpg secret keys not migrated after upgrade to gnupg 2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1565963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
