Re: OT: Re: Removing hkp from server

2015-05-16 Thread Juan Miguel Navarro Martínez
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Jerry: > On Sat, 16 May 2015 11:37:12 +0200, Werner Koch stated: > >> FWIW: GnuPG 2.1 creates revocation certifciates for all new keys >> and stores them below ~/.gnupg/openpgp-recovs.d/. > > I have created new keys; however, they are not located i

Re: Receiving keys by PKA or OpenPGP

2015-05-16 Thread Daniel Baur
Hello, Am 15.05.2015 um 13:33 schrieb Werner Koch: > gpg2 --auto-key-locate clear,nodefault,pka --locate-key ADDRESS ah ok, thanks. I forgot to consult the man-page for gpg2, sorry. Sincerely, DaB. ___ Gnupg-users mailing list Gnupg-users@gnupg.or

OT: Re: Removing hkp from server

2015-05-16 Thread Jerry
On Sat, 16 May 2015 11:37:12 +0200, Werner Koch stated: > FWIW: GnuPG 2.1 creates revocation certifciates for all new keys and > stores them below ~/.gnupg/openpgp-recovs.d/. I have created new keys; however, they are not located in that folder. The only key I have there is for the very first one

Re: What Linux kernel configuration options are required by GPG for --refresh-keys?

2015-05-16 Thread Werner Koch
On Fri, 15 May 2015 16:36, d...@fifthhorseman.net said: > shouldn't dirmngr know enough to stop trying v6 addresses when v6 isn't > available? Adding v6 support at runtime would then require a restart. The real bug is that dirmngr does not mark the v6 address dead and retry anotyer server (or th

Re: Removing hkp from server

2015-05-16 Thread Werner Koch
On Fri, 15 May 2015 21:49, juanmi.3...@gmail.com said: > Next time create revocation certs and let the key expire as well, as > you can later extend the expiration date. FWIW: GnuPG 2.1 creates revocation certifciates for all new keys and stores them below ~/.gnupg/openpgp-recovs.d/. Salam-Shal

Re: gnupg migration corrupt db?

2015-05-16 Thread Werner Koch
On Fri, 15 May 2015 13:57, berend.de.schou...@gmail.com said: > They do. But I don't want to keep two gnupg versions installed > indefinitely, and use different binaries for different keys. That's > madness. Those few folks who still use their old insecure PGP-2 keys need to keep 1.4 around. I

Re: gnupg migration corrupt db?

2015-05-16 Thread Berend De Schouwer
On Fri, 2015-05-15 at 20:28 +0100, MFPA wrote: > > > How do I check if they are PGP2 keys? > > If they are, they will have a shorter fingerprint which is commonly > presented as 16 separate double hex digits. > ; Then no, they are not PGP2