-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: fix the unavailable server address #39731
Conversation
Due to even more GDPR takedown requests, the DNS records for the pool will no longer be provided at all.
see also nodejs/node#39731 Signed-off-by: rick <1450685+LinuxSuRen@users.noreply.github.com>
see also nodejs/node#39731 Signed-off-by: rick <1450685+LinuxSuRen@users.noreply.github.com>
cc @nodejs/releasers |
I'm not sure either, but there are other working .com/.net/.org sites listed as well. How does one pick? Including both a text table and a screenshot of that
|
We'll probably want to avoid the sks keyservers. #39227 proposes keys.openpgp.org and/or keys.ubuntu.com. Probably longer term we'll switch over to https://github.com/nodejs/release-keys when it is ready. |
Closing in favor of #39227. |
Due to even more GDPR takedown requests, the DNS records
pool.sks-keyservers.net
for the pool will no longer be provided at all. See also the following screenshot:I'm not sure if the address
sks.srv.dumain.com
is perfect as a default one. But I take it from https://sks-keyservers.net/status/.