From: Cynede <cynede@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] pre-GLEP: Gentoo OpenPGP web of trust
Date: Fri, 01 Feb 2019 18:17:33 +0400 [thread overview]
Message-ID: <669c7c1c053bb2845459a22c83d8c8322020aafa.camel@gentoo.org> (raw)
In-Reply-To: <3018116.TxlsP8b7va@porto>
[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]
On Fri, 2019-02-01 at 13:47 +0100, Andreas K. Huettel wrote:
> > I don't see anything in glep 76 about requiring verification of the
> > signatures. It's my view (as trustee) that assertation by the
> > signer
> > that 'this is my signature' is sufficient.
>
> ^ This.
>
> It's not our business to check IDs, and it's not our business to
> stalk people
> on google or facebook.
>
> Now if someone says "Here's my name, and actually it is a fake name",
> then
> that is a reason to refuse commit rights or patch acceptance, and
> probably ask
> for some sort of verification when another name is then given.
>
> (That behaviour is roughly as intelligent as walking up to the
> security guy at
> the airport and claiming loudly "I have a bomb in my luggage.")
>
> Apart from that, I dont think we should care.
>
I agree.
I'd like Gentoo to support pseudonyms (for the purposes of privacy) as
FSF projects does, and in that case ID/webcam verification with OpenPGP
keys being signed by members of trustee makes real sense. (probably
that could be off-topic here)
Cynede
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2019-02-01 14:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 13:56 [gentoo-project] pre-GLEP: Gentoo OpenPGP web of trust Michał Górny
2019-01-31 14:21 ` Brian Evans
2019-01-31 15:33 ` Matthew Thode
2019-02-01 2:48 ` Sam Jorna (wraeth)
2019-02-01 6:57 ` Michał Górny
2019-02-01 14:43 ` Brian Evans
2019-02-02 6:00 ` desultory
2019-01-31 15:32 ` Matthew Thode
2019-02-01 12:47 ` Andreas K. Huettel
2019-02-01 14:17 ` Cynede [this message]
2019-02-01 14:32 ` Rich Freeman
2019-02-01 14:53 ` Kristian Fiskerstrand
2019-02-01 17:27 ` Kristian Fiskerstrand
2019-02-01 20:46 ` Rich Freeman
2019-02-02 6:02 ` desultory
2019-02-01 14:20 ` Michał Górny
2019-01-31 16:33 ` Kristian Fiskerstrand
2019-01-31 16:35 ` Alec Warner
2019-01-31 20:29 ` Kristian Fiskerstrand
2019-01-31 21:40 ` Alec Warner
2019-01-31 22:00 ` Kristian Fiskerstrand
2019-01-31 22:49 ` Michael Orlitzky
2019-02-01 0:09 ` Rich Freeman
2019-02-01 0:47 ` Kristian Fiskerstrand
2019-01-31 17:33 ` Rich Freeman
2019-02-01 12:51 ` Andreas K. Huettel
2019-02-01 13:25 ` Michał Górny
2019-02-02 5:55 ` desultory
2019-02-02 13:47 ` Rich Freeman
2019-01-31 19:25 ` Kristian Fiskerstrand
2019-02-01 0:41 ` Chris Reffett
2019-02-01 0:42 ` Kristian Fiskerstrand
2019-02-01 0:55 ` Chris Reffett
2019-02-01 1:56 ` Rich Freeman
2019-02-01 12:52 ` Andreas K. Huettel
2019-02-02 5:54 ` desultory
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=669c7c1c053bb2845459a22c83d8c8322020aafa.camel@gentoo.org \
--to=cynede@gentoo.org \
--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