public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] implementation details for GLEP 41
Date: Sat, 19 Nov 2005 12:45:38 -0600	[thread overview]
Message-ID: <20051119184538.GE25937@nightcrawler> (raw)
In-Reply-To: <20051119170615.GW12982@mail.lieber.org>

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

On Sat, Nov 19, 2005 at 05:06:15PM +0000, Kurt Lieber wrote:
> For instance, the way GLEP 41 suggests doing r/o cvs is not going to work.
> It suggests using a single account and placing an SSH key for each arch
> tester in that account's ~/.ssh/authorized_keys file.
text in question

"Get read-only access to the gentoo-x86 repository. This doesn't have 
to be individual accounts, a single account, without a shell, with all 
of their keys will be sufficiant."

Note the "doesn't have to be" and "will be sufficient", it's left open 
to how y'all want to implement it.

> There are no provisions for key management and I cannot see an easy way to
> handle it.  It's easy to add new keys, but how do we clean out old keys for
> retired arch testers?  (including arch testers that "retire" without ever
> informing us)  SSH doesn't log key ID as near as I can tell, so we have no
> way of tracking what keys are used and how often.  Also, how do we
> definitively correlate an SSH key with an arch tester?  
> 
> Now, the same question for email -- how do we manage aliases, especially
> for inactive, retired and semi-retired arch testers?  We could track usage
> in logs, but between mailing list subscriptions, bugzilla notifications and
> all sorts of other automated emails, that's not an accurate representation
> of whether an email alias is actively used or not.
> 
> I talked to Lance and neither he nor I were consulted about this GLEP and
> how feasible the implementation is.  We both are quite concerned about the
> issues that I've outlined above as well as others.  
> 
> This isn't a "we're refusing to implement this GLEP" email, btw, though I'm
> sure some of you will take it as such.  It is, however, a "we were never
> consulted regarding implementation details, so there are still issues that
> need to be worked out before this GLEP can go anywhere" email.  

Cvs concerns above are all based upon doing single account for cvs ro; 
again, it's stated as an option (iow, the option is left up to y'all).

It's not mandating anything on you for cvs, reread it if you don't 
believe me.  It's stating the base, that they only need the users to 
have cvs ro access...

Either way, it's word games, and yes, it's kind of retarded.
~harring

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

  parent reply	other threads:[~2005-11-19 18:48 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-19 17:06 [gentoo-dev] implementation details for GLEP 41 Kurt Lieber
2005-11-19 17:57 ` Danny van Dyk
2005-11-19 18:15   ` Kurt Lieber
2005-11-19 18:34     ` Simon Stelling
2005-11-19 18:45 ` Brian Harring [this message]
2005-11-19 19:03 ` Sven Vermeulen
2005-11-19 19:14   ` Kurt Lieber
2005-11-19 19:51     ` Brian Harring
2005-11-19 22:03       ` Kurt Lieber
2005-11-19 22:13         ` Lares Moreau
2005-11-19 22:30         ` Brian Harring
2005-11-19 22:47           ` Kurt Lieber
2005-11-19 22:52             ` Brian Harring
2005-11-19 23:04               ` Kurt Lieber
2005-11-20  0:26                 ` Retiring devs [was Re: [gentoo-dev] implementation details for GLEP 41] Brian Harring
2005-11-20  8:07                   ` Sune Kloppenborg Jeppesen
2005-11-20 12:58                   ` Wernfried Haas
2005-11-20 15:10                   ` Bryan Ãstergaard
2005-11-20 15:34                     ` Lance Albertson
2005-11-20 15:43                       ` Bryan Ãstergaard
2005-11-20 16:52                         ` Ned Ludd
2005-11-20 19:40                     ` Wernfried Haas
2005-11-19 23:04             ` [gentoo-dev] implementation details for GLEP 41 Tres Melton
2005-11-19 23:09               ` Lance Albertson
2005-11-19 23:33                 ` Simon Stelling
2005-11-20  4:27             ` Grant Goodyear
2005-11-19 22:42 ` Kurt Lieber
2005-11-19 22:44   ` Dan Meltzer
2005-11-19 22:56     ` Kurt Lieber
2005-11-19 22:57       ` Dan Meltzer
2005-11-19 22:59       ` Dan Meltzer
2005-11-19 23:12         ` Kurt Lieber
2005-11-19 23:44       ` Lares Moreau
2005-11-20  0:13         ` Lance Albertson
2005-11-20  0:28           ` Lares Moreau
2005-11-20  1:02             ` Lance Albertson
2005-11-20  1:41               ` Lares Moreau
2005-11-20  4:25   ` Grant Goodyear
2005-11-20  4:37     ` Ned Ludd
2005-11-20  4:49       ` Lance Albertson
2005-11-20  4:42     ` Corey Shields
2005-11-20  4:50       ` Lance Albertson
2005-11-20  5:04         ` Corey Shields
2005-11-20  5:44           ` Robin H. Johnson
2005-11-20 11:29             ` [gentoo-dev] " Duncan
2005-11-20 14:49               ` Lares Moreau
2005-11-20 14:57                 ` Ciaran McCreesh
2005-11-21 11:48                   ` [gentoo-dev] " Duncan
2005-11-20 16:37                 ` [gentoo-dev] " Corey Shields
2005-11-20  5:31         ` [gentoo-dev] CVS-Server requirements (was: implementation details for GLEP 41) Lars Weiler
2005-11-20 14:44           ` Lares Moreau

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=20051119184538.GE25937@nightcrawler \
    --to=ferringb@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