From: "R. Tyler Ballance" <tyler@slide.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Jakub Narebski <jnareb@gmail.com>, m.arya@yahoo.com, git@vger.kernel.org
Subject: Re: Few Questions
Date: Wed, 21 Jan 2009 03:08:43 -0800 [thread overview]
Message-ID: <1232536123.3477.638.camel@starfruit> (raw)
In-Reply-To: <20090120160410.GI14053@spearce.org>
On Tue, 2009-01-20 at 08:04 -0800, Shawn O. Pearce wrote:
> <plug type="not-quite-ready-but-will-be-soon">
>
> Gerrit2 is also likely to enter this "market" soon. I'm trying to
> get it production ready and live for one major project before the
> end of this month. It embeds its own SSH daemon on a non-standard
> port, completely disconnected from the OS authentication. This may
> make it slightly more palatable in some enviroments then Gitosis,
> as you don't need a huge authorized_keys file, and you don't have
> to worry quite so much about attack vectors.
> </plug>
>
<plug type="not-really-existent-yet-but-gee-golly-i-wish-it-were"
variant="mildly-offtopic" unnecessary:attribute="is-unnecessary">
I talked with Chris Wanstrath (defunkt) of Git Hub once upon a time
about them open sourcing their additions onto the openSSH sshd(8) to
work public key lookup into a MySQL database instead of simply reading a
flat file.
It'd be nice to add some peer pressure to get them to release it
already ;)
</plug>
I read your thread(s) on groups.google.com regarding Gerrit2 and it
seems quite promising as well. Looking forward to it being ready ;)
Cheers
--
-R. Tyler Ballance
Slide, Inc.
prev parent reply other threads:[~2009-01-21 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 10:38 Few Questions Arya, Manish Kumar
2009-01-20 11:04 ` Matthieu Moy
2009-01-20 15:44 ` Jakub Narebski
2009-01-20 16:04 ` Shawn O. Pearce
2009-01-21 11:08 ` R. Tyler Ballance [this message]
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=1232536123.3477.638.camel@starfruit \
--to=tyler@slide.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=m.arya@yahoo.com \
--cc=spearce@spearce.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;
as well as URLs for NNTP newsgroup(s).