public inbox for [email protected]  

help / color / mirror / Atom feed

From: David Fetter <[email protected]>
To: Magnus Hagander <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: [email protected]
Subject: Re: Git access?
Date: Tue, 10 Jun 2008 15:00:32 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Tue, Jun 10, 2008 at 09:14:35PM +0200, Magnus Hagander wrote:
> David Fetter wrote:
> > On Fri, Jun 06, 2008 at 01:54:43PM +0200, Peter Eisentraut wrote:
> >> The plan is to try out gitosis for account management.
> > 
> > It's an interesting plan, but it's one that's preventing people
> > from using the service.  How about shelving that plan for the
> > moment and handing out access as needed to developers? :)
> 
> Please don't. Handing more access out in an uncontrolled way will
> give us a lot more work cleaning things up later.

With respect, I must disagree.  This resource is incredibly easy to
maintain--and practically useless--because nobody can get on there.

If somebody or somebodies here is thinking about some kind of single
sign-on[1] system for developers, let's discuss that separately.  I
don't recall anybody deciding that we were going to use one, and I
certainly don't recall that it's been decided that that decision gates
access to git.postgresql.org.

Cheers,
David.

[1]  For me, "single sign-on" reads as "high-value target" from an
attacker's point of view, and I generally think the convenience isn't
worth the cascading failure modes such systems have.
-- 
David Fetter <[email protected]> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: [email protected]

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

view thread (12+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Git access?
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox