From c4faf7d38264352c8c2861edac022312c173ab7e Mon Sep 17 00:00:00 2001 From: Guillem Jover Date: Sat, 23 Mar 2024 03:39:43 +0100 Subject: Update keyservers to point to keys.openpgp.org --- english/devel/join/nm-step2.wml | 2 +- english/events/keysigning.wml | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) (limited to 'english') diff --git a/english/devel/join/nm-step2.wml b/english/devel/join/nm-step2.wml index 0fec6984e9a..49cbf96fcf5 100644 --- a/english/devel/join/nm-step2.wml +++ b/english/devel/join/nm-step2.wml @@ -24,7 +24,7 @@ see the README file in the debian-keyring package.

Each Applicant must provide an OpenPGP version 4 public key with encryption capabilities. The preferred way to do this is to export it to one of the public key -servers, such as subkeys.pgp.net. +servers, such as keys.openpgp.org. Public keys can be exported using:

 gpg --send-key --keyserver <server address> <yourkeyid>
diff --git a/english/events/keysigning.wml b/english/events/keysigning.wml
index 8ad94e123ac..cbe5156e125 100644
--- a/english/events/keysigning.wml
+++ b/english/events/keysigning.wml
@@ -11,8 +11,8 @@ interesting.

session. Note that all examples use keyring.debian.org as the keyserver. If the key in question is not in the Debian keyring, replace keyring.debian.org with a public -keyserver like wwwkeys.pgp.net (which despite the name -also stores OpenPGP keys.)

+keyserver like keys.openpgp.org (which is a validating +key server).

People should only sign a key under at least two conditions:

-- cgit v1.2.3