From: Philip Kaludercic <philipk@posteo.net>
To: CHENG Gao via "Emacs development discussions." <emacs-devel@gnu.org>
Cc: CHENG Gao <chenggao@icloud.com>
Subject: Re: [Reminder]Decommissoned keyservers
Date: Sun, 11 Feb 2024 17:39:27 +0000 [thread overview]
Message-ID: <87r0hiyk6o.fsf@posteo.net> (raw)
In-Reply-To: <871qcndgot.fsf@icloud.com> (CHENG Gao via's message of "Sat, 18 Nov 2023 08:54:26 +0800")
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
CHENG Gao via "Emacs development discussions." <emacs-devel@gnu.org>
writes:
> *On Fri, 17 Nov 2023 21:15:55 +0000
> * Also sprach Philip Kaludercic <philipk@posteo.net>:
>
>> CHENG Gao via "Emacs development discussions." <emacs-devel@gnu.org>
>> writes:
>>
>>> In lisp/epa-ks.el, several keyservers were decommissioned, and guess
>>> shoule be removed:
>>>
>>> keys.gnupg.net
>>> pool.sks-keyservers.net
>>> zimmermann.mayfirst.org
>>
>> Do you have any links about this for the first two? zimmermann has a
>> notice on the front page, so I guess it can be removed.
>
> See:
>
> https://gist.github.com/rjhansen/67ab921ffb4084c865b3618d6955275f
>
> https://unix.stackexchange.com/questions/656205/sks-keyservers-gone-what-to-use-instead
So would anyone have an issue with applying this patch:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Removed-decommissioned-PGP-keyservers.patch --]
[-- Type: text/x-diff, Size: 1060 bytes --]
From cf77b918230b4403b8b5b9579fa97174edaf280c Mon Sep 17 00:00:00 2001
From: Philip Kaludercic <philipk@posteo.net>
Date: Sun, 11 Feb 2024 18:38:13 +0100
Subject: [PATCH] Removed decommissioned PGP keyservers
* lisp/epa-ks.el (epa-keyserver): Update the user option type of
`epa-keyserver'.
See https://mail.gnu.org/archive/html/emacs-devel/2023-11/msg00857.html.
---
lisp/epa-ks.el | 3 ---
1 file changed, 3 deletions(-)
diff --git a/lisp/epa-ks.el b/lisp/epa-ks.el
index c3c11bb0b0b..13840da0bd9 100644
--- a/lisp/epa-ks.el
+++ b/lisp/epa-ks.el
@@ -47,11 +47,8 @@ epa-keyserver
(repeat :tag "Random pool"
(string :tag "Keyserver address"))
(const "keyring.debian.org")
- (const "keys.gnupg.net")
(const "keyserver.ubuntu.com")
(const "pgp.mit.edu")
- (const "pool.sks-keyservers.net")
- (const "zimmermann.mayfirst.org")
(string :tag "Custom keyserver"))
:version "28.1")
--
2.39.2
[-- Attachment #3: Type: text/plain, Size: 23 bytes --]
--
Philip Kaludercic
next prev parent reply other threads:[~2024-02-11 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 10:11 [Reminder]Decommissoned keyservers CHENG Gao via Emacs development discussions.
2023-11-17 21:02 ` Jonas Bernoulli
2023-11-18 15:41 ` Philip Kaludercic
2023-11-17 21:15 ` Philip Kaludercic
2023-11-18 0:54 ` CHENG Gao via Emacs development discussions.
2024-02-11 17:39 ` Philip Kaludercic [this message]
2024-02-17 18:13 ` Stefan Kangas
2024-02-17 18:48 ` Philip Kaludercic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0hiyk6o.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=chenggao@icloud.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).