From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <overseers-return-9644-listarch-overseers=sources.redhat.com@sourceware.org>
Received: (qmail 19415 invoked by alias); 29 Sep 2007 02:00:07 -0000
Received: (qmail 19174 invoked by uid 22791); 29 Sep 2007 02:00:05 -0000
X-Spam-Check-By: sourceware.org
Received: from nz-out-0506.google.com (HELO nz-out-0506.google.com) (64.233.162.232)
    by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 29 Sep 2007 02:00:03 +0000
Received: by nz-out-0506.google.com with SMTP id s1so7187152nze
        for <overseers@gcc.gnu.org>; Fri, 28 Sep 2007 19:00:00 -0700 (PDT)
Received: by 10.114.80.4 with SMTP id d4mr1016998wab.1191031200064;
        Fri, 28 Sep 2007 19:00:00 -0700 (PDT)
Received: by 10.114.149.7 with HTTP; Fri, 28 Sep 2007 19:00:00 -0700 (PDT)
Message-ID: <4aca3dc20709281900g4db8af17hae1bca68bf85e51d@mail.gmail.com>
Date: Sat, 29 Sep 2007 02:00:00 -0000
From: "Daniel Berlin" <dberlin@dberlin.org>
To: "Ian Lance Taylor" <iant@google.com>
Subject: Re: [NightStrike <nightstrike@gmail.com>] SVN access over https (SSL)
Cc: overseers@gcc.gnu.org, NightStrike <nightstrike@gmail.com>
In-Reply-To: <m3tzpe45xg.fsf@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <m3ejgi5mvw.fsf@localhost.localdomain>
	 <4aca3dc20709281741j346345bs8fd4ad1fb9967e99@mail.gmail.com>
	 <m3tzpe45xg.fsf@localhost.localdomain>
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/msg00138.txt.bz2

Most people who proxy https proxy http as well.


On 28 Sep 2007 18:27:23 -0700, Ian Lance Taylor <iant@google.com> wrote:
> "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?
>