From: Roy Bamford <neddyseagoon@gentoo.org>
To: Matthew Thode <mthode@mthode.org>
Cc: Ulrich Mueller <ulm@gentoo.org>,
gentoo-nfp@lists.gentoo.org, trustees@gentoo.org
Subject: [gentoo-nfp] Re: PGP fingerprints of Foundation members (item for Trustees meeting)
Date: Thu, 03 Aug 2017 19:23:11 +0100 [thread overview]
Message-ID: <I6Clo4HzDkRyqsJmbSMsz1@1kxnj5prLVf01jtbzNDSI> (raw)
In-Reply-To: <d00da10a-83b7-409b-9842-e5e07d024736@email.android.com> (from mthode@mthode.org on Thu Aug 3 12:16:31 2017)
[-- Attachment #1: Type: text/plain, Size: 1491 bytes --]
On 2017.08.03 12:16, Matthew Thode wrote:
> To be clear, a list of full key IDs with verification (some sort of
> video chat maybe) of the fingerprint. Said fingerprint would be
> recorded in git (signed commits and pushes to verify trust of the
> fingerprints).
>
> On August 3, 2017 6:13:13 AM CDT, Ulrich Mueller <ulm@gentoo.org>
> wrote:
> >As discussed with prometheanfire in #gentoo-trustees, I am suggesting
> >the following as an item for the (September?) Trustees meeting.
> >
> >Apparently, the Foundation only has a list of PGP key IDs in
> >https://wiki.gentoo.org/wiki/Foundation:Member_List. Even worse, most
> >IDs listed there are only 32 bit IDs, providing no security at all.
> >
> >I would like to ask the Foundation to keep a list with the (160 bit)
> >PGP fingerprints of its members. (For developers, this information
> >should be readily available in LDAP.)
> >
> >Ulrich
>
> --
> Sent from Kaiten Mail. Please excuse my brevity.
What do we need to prove?
That the the key belongs to a given individual or just that the key on the vote
is the same as the key used for the membership application.?
The former involves a web of trust of some sort and we don't do that for devs
joining the distro.
I suggest that the latter is suffcient but the web of trust would be nice to have.
Agreed tht the 32 bit key IDs need to be improved.
--
Regards,
Roy Bamford
(Neddyseagoon) a member of
elections
gentoo-ops
forum-mods
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-08-03 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 11:13 [gentoo-nfp] PGP fingerprints of Foundation members (item for Trustees meeting) Ulrich Mueller
[not found] ` <d00da10a-83b7-409b-9842-e5e07d024736@email.android.com>
2017-08-03 18:23 ` Roy Bamford [this message]
2017-08-03 23:19 ` [gentoo-nfp] " Sam Jorna
2017-08-05 10:17 ` Andrew Savchenko
2017-08-04 3:51 ` Andreas K. Huettel
2017-08-04 4:09 ` Matthew Thode
2017-08-04 4:14 ` Doug Freed
2017-08-03 23:29 ` [gentoo-nfp] " M. J. Everitt
2017-11-26 21:06 ` Daniel Campbell
2017-11-26 21:13 ` David Abbott
2017-11-27 3:05 ` Daniel Campbell
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=I6Clo4HzDkRyqsJmbSMsz1@1kxnj5prLVf01jtbzNDSI \
--to=neddyseagoon@gentoo.org \
--cc=gentoo-nfp@lists.gentoo.org \
--cc=mthode@mthode.org \
--cc=trustees@gentoo.org \
--cc=ulm@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