From: kuzetsa <kuzetsa@gmail.com>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Repo mirror & CI: official statement wrt GitHub
Date: Thu, 14 Jun 2018 22:27:14 -0400 [thread overview]
Message-ID: <933a84d7-2dc3-e77a-0444-ccc4aa20eb26@gmail.com> (raw)
In-Reply-To: <72b16227-ad16-eca1-5f35-994fe7e89e2c@gentoo.org>
On 06/14/2018 08:26 PM, Thomas Deutschmann wrote:
> GitHub's feature to display "verified" status has zero meaning for the
> Gentoo project. We only trust our own key store.
>
> But this all doesn't matter:
> GitLab for example offers a similar feature. I.e. you can add your
> public key to your GitLab.com account like you did with your GitHub.com
> account and GitLab will display the same "verified" indicator.
I think I understand that viewpoint, but there's nuance:
(it matters "more than zero", as you claimed)
if proxy-maintainers or other contributors have no
assurance that they aren't being impersonated, then
a person in bad faith could spoof a submission.
it's a matter of convenience for the committing dev
to be able to verify my key was used for a commit.
I'm aware that a gentoo developer who does the actual
commit will use their own key for the commit which
is entered into the proper git tree.
It's still a matter of convenience. an assurance that
there's some way which contributors can have "not zero"
trust that a commit wasn't wrongly made on their behalf
(malicious chain of custody on some level)
(TIL - as you say, gitlab has this feature too. cool)
--kuza
next prev parent reply other threads:[~2018-06-15 2:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-09 7:25 [gentoo-project] Repo mirror & CI: official statement wrt GitHub Michał Górny
2018-06-09 7:50 ` Ulrich Mueller
2018-06-09 7:52 ` Michał Górny
2018-06-09 9:11 ` Thomas Deutschmann
2018-06-11 12:15 ` Kristian Fiskerstrand
2018-06-11 13:28 ` Rich Freeman
2018-06-14 9:47 ` James Le Cuirot
2018-06-14 14:14 ` Alec Warner
2018-06-14 14:25 ` Mauricio Lima Pilla
2018-06-15 0:33 ` Thomas Deutschmann
2018-06-15 1:14 ` Aaron W. Swenson
2018-06-15 2:16 ` Alec Warner
2018-06-15 7:20 ` Kristian Fiskerstrand
2018-06-16 23:55 ` Virgil Dupras
2018-06-17 0:25 ` Rich Freeman
2018-06-16 21:58 ` Andreas K. Huettel
2018-06-16 23:14 ` Rich Freeman
2018-06-16 23:45 ` Alec Warner
2018-06-17 1:05 ` Brian Dolbec
2018-06-14 19:55 ` kuzetsa
2018-06-15 0:26 ` Thomas Deutschmann
2018-06-15 2:27 ` kuzetsa [this message]
2018-06-15 11:50 ` Thomas Deutschmann
2018-06-15 14:55 ` kuzetsa
2018-06-15 15:31 ` Rich Freeman
2018-06-15 16:03 ` kuzetsa
2018-06-15 16:11 ` Rich Freeman
2018-06-15 16:22 ` kuzetsa
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=933a84d7-2dc3-e77a-0444-ccc4aa20eb26@gmail.com \
--to=kuzetsa@gmail.com \
--cc=gentoo-project@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