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

[Mario Limonciello]

Yes that would be great, thanks

On Sat, Apr 9, 2016, 14:05 dkg <dkg at fifthhorseman.net> wrote:

> 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?
>
>    --dkg
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> 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
>

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gnupg2 in Ubuntu.
https://bugs.launchpad.net/bugs/1565963

Title:
  gpg secret keys not migrated after upgrade to gnupg 2.1

Status in gnupg2 package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to gnupg 2.1 I can no longer see my keys in seahorse
  (Passwords and Keys in apps scope in unity) and evolution cannot find
  my gpg keys. Someone said this might be related to
  https://www.gnupg.org/faq/whats-new-in-2.1.html#autostart and
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796931

  Reading the Debian bug I see someone mentioned that running this might help:
  $ gpg2 --import < ./.gnupg/secring.gpg

  I did that and gpg2 went through each of my private keys to import
  them. When done I logged out and back in and seahorse saw my keys. I'm
  not sure why gpg2 didn't prompt me before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1565963/+subscriptions