From: "Shawn O. Pearce" <spearce@spearce.org>
To: Tom Lanyon <tom@netspot.com.au>
Cc: git@vger.kernel.org
Subject: Re: Internal, corporate, shared hosting solutions
Date: Fri, 26 Sep 2008 08:39:03 -0700 [thread overview]
Message-ID: <20080926153903.GC17584@spearce.org> (raw)
In-Reply-To: <8B29890D-C03B-4ECE-9BEF-0A8E8EF7233E@netspot.com.au>
Tom Lanyon <tom@netspot.com.au> wrote:
> We have some pretty basic requirements:
> - authentication and authorisation; some repos are only readable/
> writable by specific people
> - accessible; many dev servers are on private subnets, ideally we need
> to be able to proxy git access
> - not too much messing with unix user accounts on the central git host
> (because they're tied to LDAP, for example)
Use git over ssh, but use gitosis on the server side:
http://scie.nti.st/2007/11/14/hosting-git-repositories-the-easy-and-secure-way
Have each developer supply their own SSH public key, install it
into the gitosis database, and they can only read/write repos
they have access to in the admin database.
Secure, fast, yea, you can actually pick two out of two. :)
--
Shawn.
next prev parent reply other threads:[~2008-09-26 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-26 15:13 Internal, corporate, shared hosting solutions Tom Lanyon
2008-09-26 15:39 ` Shawn O. Pearce [this message]
2008-09-26 18:17 ` Johan Herland
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=20080926153903.GC17584@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=tom@netspot.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.