From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <overseers-return-9643-listarch-overseers=sources.redhat.com@sourceware.org>
Received: (qmail 7251 invoked by alias); 29 Sep 2007 01:27:50 -0000
Received: (qmail 7244 invoked by uid 22791); 29 Sep 2007 01:27:50 -0000
X-Spam-Check-By: sourceware.org
Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.45.13)
    by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 29 Sep 2007 01:27:47 +0000
Received: from zps76.corp.google.com (zps76.corp.google.com [172.25.146.76])
	by smtp-out.google.com with ESMTP id l8T1RhSn006844;
	Fri, 28 Sep 2007 18:27:43 -0700
Received: from smtp.corp.google.com (spacemonkey2.corp.google.com [192.168.120.114])
	by zps76.corp.google.com with ESMTP id l8T1RdUx006536
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 28 Sep 2007 18:27:39 -0700
Received: from localhost.localdomain.google.com (19.sub-75-208-199.myvzw.com [75.208.199.19])
	(authenticated bits=0)
	by smtp.corp.google.com (8.13.8/8.13.8) with ESMTP id l8T1RZuB008019
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Fri, 28 Sep 2007 18:27:38 -0700
To: "Daniel Berlin" <dberlin@dberlin.org>
Cc: overseers@gcc.gnu.org, NightStrike <nightstrike@gmail.com>
Subject: Re: [NightStrike <nightstrike@gmail.com>] SVN access over https (SSL)
References: <m3ejgi5mvw.fsf@localhost.localdomain>
	<4aca3dc20709281741j346345bs8fd4ad1fb9967e99@mail.gmail.com>
From: Ian Lance Taylor <iant@google.com>
Date: Sat, 29 Sep 2007 01:27:00 -0000
In-Reply-To: <4aca3dc20709281741j346345bs8fd4ad1fb9967e99@mail.gmail.com>
Message-ID: <m3tzpe45xg.fsf@localhost.localdomain>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Mailing-List: contact overseers-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <overseers.sourceware.org>
List-Archive: <http://sourceware.org/ml/overseers/>
List-Post: <mailto:overseers@sourceware.org>
List-Help: <mailto:overseers-help@sourceware.org>,
	<http://sourceware.org/ml/#faqs>
Sender: overseers-owner@sourceware.org
X-SW-Source: 2007-q3/txt/msg00137.txt.bz2

"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?