public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kurt Lieber <klieber@gentoo.org>
To: Tavis Ormandy <taviso@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Finger GLEP
Date: Mon, 11 Aug 2003 09:33:14 -0400	[thread overview]
Message-ID: <20030811133311.GP1819@mail.lieber.org> (raw)
In-Reply-To: <20030811113518.GA29154@sdf.lonestar.org>

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

On Mon, Aug 11, 2003 at 11:35:19AM +0000 or thereabouts, Tavis Ormandy wrote:
> Well, however you choose to distribute keys theres the problem of
> getting everybody to create one..thats hardly a huge issue, and the
> problem exists for every method of distribution..using a keys.gentoo.org
> webserver is still "rendered useless" if you cant get everybody to
> generate and upload a key, how do you propose to deal with that?

The efforts we have underway with secure portage will require developers to
have and maintain a GPG key.  It will also require them to place said key
on a public keyserver.  

> none of the issues apply solely to my solution, and im certain the
> benefits outweigh the drawbacks.

Well, at this point, I'm inclined to reject this GLEP and/or ask you to
re-work it to incorporate some of the changes suggested by myself and
others.  Specifically: 

* Data needs to be maintained in one central repository.  
* I'm not opposed to offering fingerd as a means of data transport, as long
  as it pulls data from the central repository mentioned above.
* I'd also be open to allowing devs the option of *supplementing* the
  information available via fingerd by creating a .plan or whatever.
  However, the core info (GPG key, name, herds info, etc.) needs to be
  maintained in the central repository.

Basically, I see the benefits of offering fingerd as a service to our users
and am willing to support that, infrastructure-wise.  I do not agree,
however, that fingerd should be the *primary* method of distributing this
info, nor do I support the idea of storing critical information such as GPG
keys in developer home dirs -- at least not as the primary "official"
repository.

--kurt

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2003-08-11 13:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-10 22:39 [gentoo-dev] Finger GLEP Tavis Ormandy
2003-08-10 23:27 ` Kurt Lieber
2003-08-10 23:36   ` Seemant Kulleen
2003-08-11  0:17     ` Tavis Ormandy
2003-08-11  0:57       ` Spider
2003-08-11  0:02   ` Tavis Ormandy
2003-08-11  9:22     ` Kurt Lieber
2003-08-11 11:35       ` Tavis Ormandy
2003-08-11 12:37         ` Paul de Vrieze
2003-08-11 12:59           ` Tavis Ormandy
2003-08-11 13:33         ` Kurt Lieber [this message]
2003-08-11 14:01           ` Tavis Ormandy
2003-08-11  0:03   ` Grant Goodyear
2003-08-11  8:05   ` Paul de Vrieze
2003-08-11  1:17 ` Aron Griffis
2003-08-11  8:24   ` Paul de Vrieze
2003-08-11 12:09     ` Tavis Ormandy

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=20030811133311.GP1819@mail.lieber.org \
    --to=klieber@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=taviso@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