From: "Thomas Deutschmann" <whissi@gentoo.org>
To: <gentoo-dev@lists.gentoo.org>
Subject: RE: [gentoo-dev] GPG key refresh
Date: Tue, 15 Dec 2020 17:11:47 +0100 [thread overview]
Message-ID: <001301d6d2fc$fee96af0$fcbc40d0$@gentoo.org> (raw)
In-Reply-To: <162d8d9f-4325-eb1e-f1cc-042acfb67973@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
Hi,
glad it's now working for you. In the meanwhile we are looking into issues with the European Gentoo server 😉
> And FWIW this sentence is a little misleading if the SKS refresh
> frequency is zero =)
>
> The SKS keyserver pool can take much longer to replicate over the
> keyserver network, while the Gentoo developer tooling explicitly
> checks the Gentoo keyserver pool with a much higher frequency.
What do you mean exactly?
For Gentoo tooling, only Gentoo keyservers are important and Gentoo no longer synchronizes with any other pool.
However, developers should still upload keys to public pools, like the SKS keyservers, so others can find the key in case they want to verify checksum or securely exchange encrypted/signed messages with Gentoo developers.
--
Regards,
Thomas
[-- Attachment #2: openpgp-digital-signature.asc --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2020-12-15 16:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 18:59 [gentoo-dev] GPG key refresh Michael Orlitzky
2020-12-14 19:17 ` Alec Warner
2020-12-14 19:41 ` Michael Orlitzky
2020-12-15 15:27 ` Thomas Deutschmann
2020-12-15 15:44 ` Michael Orlitzky
2020-12-15 15:49 ` Michael Orlitzky
2020-12-15 16:11 ` Thomas Deutschmann [this message]
2020-12-15 16:16 ` Michael Orlitzky
2020-12-16 4:37 ` Aaron W. Swenson
2020-12-16 8:01 ` Michał Górny
2020-12-17 4:48 ` desultory
2020-12-17 18:28 ` Mike Gilbert
2020-12-17 19:23 ` Michał Górny
2020-12-17 18:35 ` Mike Gilbert
2020-12-17 19:22 ` Michał Górny
2020-12-14 19:24 ` Cédric Krier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001301d6d2fc$fee96af0$fcbc40d0$@gentoo.org' \
--to=whissi@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox