On Thu, Aug 16, 2018 at 06:31:41PM -, Carlo Wood wrote:
> Note the 'skipped PGP-2 keys: 2' ?!
>
> What, why? How do I get those back?!
Hello Carlo, upstream GnuPG 2.x dropped support for the PGP-2 keys
several years ago:
https://gnupg.org/faq/whats-new-in-2.1.html#nopgp2
You can install the
On Sun 2016-04-10 08:39:48 -0400, Werner Koch wrote:
> On Sat, 9 Apr 2016 20:57, d...@fifthhorseman.net said:
>
>> Shall i open an issue in https://bugs.gnupg.org/ about this?
>
> better do that.
ok, i've created this:
https://bugs.gnupg.org/gnupg/issue2312
Thanks for the followup, Werner.
Yes that would be great, thanks
On Sat, Apr 9, 2016, 14:05 dkg wrote:
> On Sat 2016-04-09 05:53:36 -0400, Werner Koch 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 th
On Sat 2016-04-09 05:53:36 -0400, Werner Koch 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
Over on https://bugs.launchpad.net/bugs/1565963, Timo Aaltonen has found
a repeatable scenario where the secret keyring has not been successfully
migrated properly when switching over to gnupg 2.1:
On Fri 2016-04-08 12:35:05 -0300, Timo Aaltonen wrote:
> :: tjaalton@wilson:~/.gnupg> ls -al
> tota
