From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21393 invoked by alias); 29 Sep 2007 00:41:27 -0000 Received: (qmail 21386 invoked by uid 22791); 29 Sep 2007 00:41:26 -0000 X-Spam-Check-By: sourceware.org Received: from an-out-0708.google.com (HELO an-out-0708.google.com) (209.85.132.241) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 29 Sep 2007 00:41:25 +0000 Received: by an-out-0708.google.com with SMTP id c3so481131ana for ; Fri, 28 Sep 2007 17:41:23 -0700 (PDT) Received: by 10.115.54.1 with SMTP id g1mr1003939wak.1191026482461; Fri, 28 Sep 2007 17:41:22 -0700 (PDT) Received: by 10.114.149.7 with HTTP; Fri, 28 Sep 2007 17:41:22 -0700 (PDT) Message-ID: <4aca3dc20709281741j346345bs8fd4ad1fb9967e99@mail.gmail.com> Date: Sat, 29 Sep 2007 00:41:00 -0000 From: "Daniel Berlin" To: "Ian Lance Taylor" Subject: Re: [NightStrike ] SVN access over https (SSL) Cc: overseers@gcc.gnu.org, NightStrike In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: 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/msg00136.txt.bz2 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. On 28 Sep 2007 17:35:47 -0700, Ian Lance Taylor 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 > 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? > > > >