On Tue, 19 Mar 2019 12:42, gnupg-users@gnupg.org said:
> I do understand why someone decided to delegate keys.gnupg.net to someone
> else, but is that healthy for GnuPG?
gnupg.{net,com,org,de} and gpg4win.{org,de} are all owned by my company
g10 Code GmbH. whois unfortunately does not show that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, 2019-03-19 at 08:18 +0100, Werner Koch wrote:
> On Mon, 18 Mar 2019 23:09, ml-gnupg-xix@linuxwan.net said:
>
> > keys.gnupg.net is just a CNAME for hkps.pool.sks-keyservers.net. This
> > host appears to be the default for GNUpg configs.
On Mon, 18 Mar 2019 23:09, ml-gnupg-xix@linuxwan.net said:
> keys.gnupg.net is just a CNAME for hkps.pool.sks-keyservers.net. This
> host appears to be the default for GNUpg configs.
FWIW, keys.gnupg.net is a hardcoded alias in dirmngr since 2.2.7 and
thus the CNAME is not used since that
On 2019-03-18 at 23:09 +1000, Ted Cooper wrote:
> If there is a more appropriate place to post this please do let me know.
> Methods of contact and persons responsible for the sks-keyservers
> infrastructure is not obvious. Onto the problem;
The SKS Devel mailing-list is also used for Operations
Howdy,
If there is a more appropriate place to post this please do let me know.
Methods of contact and persons responsible for the sks-keyservers
infrastructure is not obvious. Onto the problem;
The hostname hkps.pool.sks-keyservers.net appears to have been pulled,
and now returns NXDOMAIN. It's
