From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19617 invoked by alias); 29 Sep 2007 05:22:35 -0000 Received: (qmail 19607 invoked by uid 22791); 29 Sep 2007 05:22:35 -0000 X-Spam-Check-By: sourceware.org Received: from py-out-1112.google.com (HELO py-out-1112.google.com) (64.233.166.176) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 29 Sep 2007 05:22:33 +0000 Received: by py-out-1112.google.com with SMTP id a29so6735084pyi for ; Fri, 28 Sep 2007 22:22:31 -0700 (PDT) Received: by 10.65.204.7 with SMTP id g7mr6363007qbq.1191043351181; Fri, 28 Sep 2007 22:22:31 -0700 (PDT) Received: by 10.65.152.18 with HTTP; Fri, 28 Sep 2007 22:22:31 -0700 (PDT) Message-ID: Date: Sat, 29 Sep 2007 05:22:00 -0000 From: NightStrike To: "Daniel Berlin" Subject: Re: [NightStrike ] SVN access over https (SSL) Cc: "Ian Lance Taylor" , overseers@gcc.gnu.org In-Reply-To: <4aca3dc20709281900g4db8af17hae1bca68bf85e51d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4aca3dc20709281741j346345bs8fd4ad1fb9967e99@mail.gmail.com> <4aca3dc20709281900g4db8af17hae1bca68bf85e51d@mail.gmail.com> Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00139.txt.bz2 On 9/28/07, Daniel Berlin wrote: > Most people who proxy https proxy http as well. proxy https is much more compatible with picky proxies than http when dealing with svn. > On 28 Sep 2007 18:27:23 -0700, Ian Lance Taylor wrote: > > "Daniel Berlin" 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 Precisely. Anonymous read access only, just like sourceforge is set up. > > > > ---------- Forwarded message ---------- > > > > From: NightStrike > > > > 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? > > >