Re: Empty keyring after upgrade to Ubuntu 18.04 :/
You could just import the old GPG files with appropriate options. I did this a while ago as my kbx got damaged when I had a hdd failure. Am 27. Juli 2018 06:50:59 MESZ schrieb fe...@crowfix.com: >I ran into a similar problem a few months ago, upgrading from a much >older gentoo system with 1.something. I don't know what specific >action fixed it, but after a couple of cycles of restoring the original >and trying different commands, it suuddenly migrated correctly. Memory >says the first couple of attempts, I tried to do something which would >have to do the migration first, and it worked when I restored the >original and did just the migration by itself. But I didn't take >enough notes to figure it out after it started working. -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Empty keyring after upgrade to Ubuntu 18.04 :/
I ran into a similar problem a few months ago, upgrading from a much older gentoo system with 1.something. I don't know what specific action fixed it, but after a couple of cycles of restoring the original and trying different commands, it suuddenly migrated correctly. Memory says the first couple of attempts, I tried to do something which would have to do the migration first, and it worked when I restored the original and did just the migration by itself. But I didn't take enough notes to figure it out after it started working. -- ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._. Felix Finch: scarecrow repairman & wood chipper / fe...@crowfix.com GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933 I've found a solution to Fermat's Last Theorem but I see I've run out of room o ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Empty keyring after upgrade to Ubuntu 18.04 :/
On Donnerstag, 26. Juli 2018 17:17:58 CEST Franek Wiertara wrote: > > On 26 Jul 2018, at 11:50, Paul M Furley wrote: > > I upgraded from Ubuntu 16.04 LTS to Ubuntu 18.04 LTS and restored my > > `.gnupg` directory from a backup disk. > > > > Now gpg doesn't see any keys... `gpg --list-keys` just exists with no > > output. > > > > I've attached the strace output of `strace gpg --list-keys`, and here's > > the output of `tree .gnupg/`: > > > > ``` > > /home/paul/.gnupg > > ├── crls.d > > │ └── DIR.txt > > ├── gpg-agent.conf > > ├── gpg-agent-info-xps > > ├── gpg.conf > > ├── hkps.pool.sks-keyservers.net.pem > > ├── openpgp-revocs.d > > │ └── [REDACTED x2].rev > > ├── private-keys-v1.d > > │ └── [REDACTED x8].key > > ├── pubring.gpg > > ├── pubring.kbx > > ├── random_seed > > ├── S.dirmngr > > ├── secring.gpg > > ├── S.gpg-agent > > ├── sshcontrol > > └── trustdb.gpg "tree .gnupg" does not list hidden files, but I guess there is a file named .gpg-v21-migrated in your .gnupg. > Is it possible the two Ubuntu distributions you mentioned ship different > versions of gnupg? Yes. In Ubuntu 18.04, gpg is actually GnuPG 2.x (according to the release notes). > I am asking about it because gnupg v. 2.0 and earlier > and gnupg v. 2.1.x and later have different ways of storing keys. I don’t > know the details because i started using gpg from version 2.1.x but this > might be where you could start to investigate the issue. gpg1 stored your private keys in secring.gpg and the public keys in pubring.gpg. gpg2 uses the private-keys-v1.d folder for private keys and pubring.kbx for public keys. When gpg2 is run for the first time, then gpg2 migrates all old keys to the new locations. Maybe you ran gpg(2) after the upgrade before you restored your .gnupg folder. To re-run the migration remove the file .gpg-v21-migrated in your .gnupg and then run gpg. Regards, Ingo ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Empty keyring after upgrade to Ubuntu 18.04 :/
Is it possible the two Ubuntu distributions you mentioned ship different versions of gnupg? I am asking about it because gnupg v. 2.0 and earlier and gnupg v. 2.1.x and later have different ways of storing keys. I don’t know the details because i started using gpg from version 2.1.x but this might be where you could start to investigate the issue. > On 26 Jul 2018, at 11:50, Paul M Furley wrote: > > Hi folks, > > I upgraded from Ubuntu 16.04 LTS to Ubuntu 18.04 LTS and restored my `.gnupg` > directory from a backup disk. > > Now gpg doesn't see any keys... `gpg --list-keys` just exists with no output. > > I've attached the strace output of `strace gpg --list-keys`, and here's the > output of `tree .gnupg/`: > > ``` > /home/paul/.gnupg > ├── crls.d > │ └── DIR.txt > ├── gpg-agent.conf > ├── gpg-agent-info-xps > ├── gpg.conf > ├── hkps.pool.sks-keyservers.net.pem > ├── openpgp-revocs.d > │ └── [REDACTED x2].rev > ├── private-keys-v1.d > │ └── [REDACTED x8].key > ├── pubring.gpg > ├── pubring.kbx > ├── random_seed > ├── S.dirmngr > ├── secring.gpg > ├── S.gpg-agent > ├── sshcontrol > └── trustdb.gpg > > 3 directories, 23 files > > ``` > > Is there anything else I can provide to help debug this? > > Thanks! > > Paul > > [unsigned... obviously ;) ] > > ___ > Gnupg-users mailing list > Gnupg-users@gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-users ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Empty keyring after upgrade to Ubuntu 18.04 :/
Hi folks,
I upgraded from Ubuntu 16.04 LTS to Ubuntu 18.04 LTS and restored my `.gnupg`
directory from a backup disk.
Now gpg doesn't see any keys... `gpg --list-keys` just exists with no output.
I've attached the strace output of `strace gpg --list-keys`, and here's the
output of `tree .gnupg/`:
```
/home/paul/.gnupg
├── crls.d
│ └── DIR.txt
├── gpg-agent.conf
├── gpg-agent-info-xps
├── gpg.conf
├── hkps.pool.sks-keyservers.net.pem
├── openpgp-revocs.d
│ └── [REDACTED x2].rev
├── private-keys-v1.d
│ └── [REDACTED x8].key
├── pubring.gpg
├── pubring.kbx
├── random_seed
├── S.dirmngr
├── secring.gpg
├── S.gpg-agent
├── sshcontrol
└── trustdb.gpg
3 directories, 23 files
```
Is there anything else I can provide to help debug this?
Thanks!
Paul
[unsigned... obviously ;) ]
execve("/usr/bin/gpg", ["gpg", "--list-keys"], 0x7fff0d450728 /* 71 vars */) = 0
brk(NULL) = 0x5628be43b000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = 0
openat(AT_FDCWD, "/etc/ld.so.preload", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
close(3)= 0
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=122497, ...}) = 0
mmap(NULL, 122497, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5a4f9f8000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libz.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\220\37\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=116960, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f5a4fa1e000
mmap(NULL, 2212016, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5a4f5d
mprotect(0x7f5a4f5ec000, 2093056, PROT_NONE) = 0
mmap(0x7f5a4f7eb000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1b000) = 0x7f5a4f7eb000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libbz2.so.1.0", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0`\23\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=66800, ...}) = 0
mmap(NULL, 2161864, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5a4f3c
mprotect(0x7f5a4f3cf000, 2093056, PROT_NONE) = 0
mmap(0x7f5a4f5ce000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xe000) = 0x7f5a4f5ce000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/libsqlite3.so.0",
O_RDONLY|O_CLOEXEC) = 3
read(3,
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\240\312\0\0\0\0\0\0"..., 832) =
832
fstat(3, {st_mode=S_IFREG|0644, st_size=1082648, ...}) = 0
mmap(NULL, 3179736, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5a4f0b
mprotect(0x7f5a4f1b3000, 2097152, PROT_NONE) = 0
mmap(0x7f5a4f3b3000, 20480, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x103000) = 0x7f5a4f3b3000
mmap(0x7f5a4f3b8000, 1240, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5a4f3b8000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libgcrypt.so.20", O_RDONLY|O_CLOEXEC) =
3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\274\0\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=1155768, ...}) = 0
mmap(NULL, 3252232, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5a4ed9
mprotect(0x7f5a4eea4000, 2093056, PROT_NONE) = 0
mmap(0x7f5a4f0a3000, 28672, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x113000) = 0x7f5a4f0a3000
mmap(0x7f5a4f0aa000, 8, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5a4f0aa000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libreadline.so.7", O_RDONLY|O_CLOEXEC)
= 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\2208\1\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=294632, ...}) = 0
mmap(NULL, 2395240, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f5a4eb4
mprotect(0x7f5a4eb81000, 2093056, PROT_NONE) = 0
mmap(0x7f5a4ed8, 32768, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x4) = 0x7f5a4ed8
mmap(0x7f5a4ed88000, 3176, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5a4ed88000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such
