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
Hi, I have the same problem; I upgraded from ubuntu 16.04 to 18.04 (one
LTS release to the next). To my astonishment afterwards I couldn't get
into my bank accounts anymore because I can't decrypt my files!
The output of the original conversion is:
>gpg --decrypt digid.nl.gpg
gpg: starting migrat
Thanks dkg, I had this issue also and setting u+x private-keys-v1.d
fixed it for me as well. As far as I know I never changed the
permissions in the .gnupg directory but you never know, could have been
years ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
dkg, you are a lifesaver as always. Setting u+x private-keys-v1.d fixed
this for me as well.
In my case, I had to do a laptop restore. I kept my gpg keys on
separate backup media - which I hadn't realized at the time was
formatted as FAT32. I no doubt "fixed" my permissions upon restore
incorre
** Bug watch added: bugs.gnupg.org/gnupg/ #2312
http://bugs.gnupg.org/gnupg/issue2312
--
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 gn
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
yeah, thanks for spotting that.. chmod u+x .gnupg/private-keys-v1.d
fixed it. Must've done a hasty chmod 600 at some point in the past!
--
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:
g
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
:: tjaalton@wilson:~/.gnupg> ls -al
total 1092
drwx-- 3 tjaalton tjaalton 4096 huhti 8 18:21 .
drwxr-xr-x 42 tjaalton tjaalton 4096 huhti 8 18:25 ..
-rw--- 1 tjaalton tjaalton 8081 maali 20 2015 gpg.conf
-rw-rw-r-- 1 tjaalton tjaalton 0 huhti 8 00:09 .gpg-v21-migrated
drw-
Since you mentioned this came from another box, can you show the
permissions for the files in .gnupg? That seems the most likely reason
for being unable to pull the files out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
and here's what happens after killing the agent and removing migration
file
gpg: starting migration from earlier GnuPG versions
gpg: porting secret keys from '/home/tjaalton/.gnupg/secring.gpg' to gpg-agent
gpg: key A88984DC/A88984DC: error sending to agent: Permission denied
gpg: error building s
trying to import keys gives:
:: tjaalton@deckard:~> gpg2 --import < ./.gnupg/secring.gpg
gpg: key A88984DC: "Timo Aaltonen " not changed
gpg: key A88984DC/A88984DC: error sending to agent: Permission denied
gpg: error building skey array: Permission denied
gpg: Total number processed: 3
gpg:
both machines were xenial -> xenial upgrades, but .gnupg directory is
older and has same origin on both (basically just copied to the laptop
at some point)
I have a third system to test things on, and I'll try to reproduce by
removing the migration file
--
You received this bug notification beca
I'm seeing this as well on two machines that I use, broke enigmail
--
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 not
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnupg2 (Ubuntu)
Status: New => Confirmed
--
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
In the default import process, i don't think i ended up needing to enter
any passwords at all. I can understand why you might need to enter
passwords when importing secret keys that weren't already in your
keyring, in general, but it seems like if being able to import them
cleanly (without passwor
I don't have any smartcards. I have three old private keys (1024D keys;
one is revoked) that I don't use any more (and therefore are not
unlocked) but 'gpg2 --import < ~/.gnupg/secring.gpg' noticed all of them
and prompted me for a password with each.
--
You received this bug notification because
thanks for your comments daniel.
I've tried to reproduce this as well and couldn't either.
I started with a Xenial VM that had an older version of gnupg2 than 2.1
installed.
I generated a key, and verified I could see it with both gpg and gpg2 as well
as in seahorse.
I then upgraded to gnupg2 2
Mario pointed me to this bug, and i'm surprised that this happened. I
also am not sure how to debug it because it's not something i've been
able to reproduce myself, and it sounds like once it's fixed for
someone, they have no incentive to go back and reproduce it themselves.
Can anyone provide a
This system started with vivid, upgraded to wily and upgraded to xenial
a few months ago. I have .gnupg/.gpg-v21-migrated but it has the
timestamp of when I ran 'gpg2 --import < ./.gnupg/secring.gpg'-- I don't
know if it was created initially and retouched when I ran the import
command later.
--
Can you comment on what version of GPG you started from on this system?
Was this system dist-upgraded a few times and did a GPG 1.x to 2.x
transition at some point?
There should be a .gnupg/.gpg-v21-migrated file. Does that exist for
you?
--
You received this bug notification because you are a
23 matches
Mail list logo
