Re: [NightStrike <nightstrike@gmail.com>] SVN access over https (SSL)

[Ian Lance Taylor <iant at google dot com>]

"Daniel Berlin" <dberlin@dberlin.org> writes:

> We'd need to generate random passwords for users, since we won't be
> able to authenticate them by ssh.
> Not really worth it, especially since this guy doesn't even have write access.

This would presumably only be for read-only anonymous access to the
sources.  I certainly agree that we shouldn't do it for write access.
Note the cited advantage of working through proxies.

Ian

> On 28 Sep 2007 17:35:47 -0700, Ian Lance Taylor <iant@google.com> wrote:
> > Redirecting to overseers in case anybody wants to take this on.  I
> > personally have no idea what would be required.
> >
> > Ian
> >
> >
> >
> > ---------- Forwarded message ----------
> > From: NightStrike <nightstrike@gmail.com>
> > To: gcc-help@gcc.gnu.org
> > Date: Thu, 27 Sep 2007 17:24:02 -0400
> > Subject: SVN access over https (SSL)
> > Currently, gcc provides access to the svn repository using the svn
> > protocol (svn://) as well as the http protocol (http://).  Some
> > sourceforge projects (not saying gcc is on sourceforge.. just citing
> > examples) also allow secure access via https.  This has the nice side
> > effect of making svn work through annoying proxies.
> >
> > Can gcc add support for https access as well as the current two methods?