public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Aaron W. Swenson" <titanofold@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GPG key refresh
Date: Tue, 15 Dec 2020 23:37:25 -0500	[thread overview]
Message-ID: <X9mPBe6imKrp+0uw@martineau.home.grandmasfridge.org> (raw)
In-Reply-To: <792e01e5-fe09-f97e-14ae-57d94cb84510@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2639 bytes --]

On 2020-12-15 11:16, Michael Orlitzky wrote:
>On 12/15/20 11:11 AM, Thomas Deutschmann wrote:
>>
>> What do you mean exactly?
>>
>> For Gentoo tooling, only Gentoo keyservers are important and Gentoo no longer synchronizes with any other pool.
>>
>"The Gentoo developer tooling explicitly checks the Gentoo keyserver
>pool with a much higher frequency" strongly implies that we check the
>non-Gentoo pools with a non-zero frequency.
>
>

I'm with Michael on this. I've recently experienced this issue myself as the
instruction to upload the key to the Gentoo keyserver is separate from the
GLEP63[1] document. It doesn't matter that the step is documented if the Holy
Tome GLEP63 doesn't mention it. What hint would I have to look for a
supplemental document to provide that specific step?

According to GLEP 63, uploading to the SKS keyserver is a requirement.
However, it fails to specify which SKS keyserver. In fact, neither "SKS" nor
"keyserver" are defined in GLEP63. Ergo, the natural interpretation is *anything*
that's called an SKS keyserver will satisfy the requirement. As long as the
developer can submit the key, the requirement is met.

Additionally, the supplemental document[2] doesn't say developers must upload
via an internal host, but that devs should upload to both SKS and the Gentoo
keyserver. Yes, it says the Gentoo keyserver is currently restricted to syncing
with "authorized Gentoo hosts", but that's a nonsense phrase and unhelpful. It
assumes I know what the authorized Gentoo hosts are. It doesn't clearly state
what they are. It kind of hints that it will pull from SKS eventually, but it
could take a long time.

I understand we temporarily stopped syncing with the public keyserver out of an
overabundance of caution. However, that shouldn't have been done without
updating every official Gentoo resource regarding how devs should handle their
keys, which as far as I know is only two documents[1,2]. A whopping 2 documents.

This new (I know it's been around for a year but that doesn't make it any less
new), stricter requirement, should be **explicitly** stated in GLEP63, properly
referencing the justification[3], and linking to the infra supplemental
document. The infra supplemental document needs to then use the phrase "must" in
place of "should" when informing readers to upload to two different locations.


Footnotes:
[1]  https://www.gentoo.org/glep/glep-0063.html

[2]  https://wiki.gentoo.org/index.php?title=Project:Infrastructure/Generating_GLEP_63_based_OpenPGP_keys&oldid=813494#Submit_your_new_key_to_the_keyserver

[3]  https://www.gentoo.org/news/2019/07/03/sks-key-poisoning.html


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-12-16  4:37 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
2020-12-15 16:16           ` Michael Orlitzky
2020-12-16  4:37             ` Aaron W. Swenson [this message]
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=X9mPBe6imKrp+0uw@martineau.home.grandmasfridge.org \
    --to=titanofold@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