From: "Daniel Berlin" <dberlin@dberlin.org>
To: "Ian Lance Taylor" <iant@google.com>
Cc: overseers@gcc.gnu.org, NightStrike <nightstrike@gmail.com>
Subject: Re: [NightStrike <nightstrike@gmail.com>] SVN access over https (SSL)
Date: Sat, 29 Sep 2007 00:41:00 -0000 [thread overview]
Message-ID: <4aca3dc20709281741j346345bs8fd4ad1fb9967e99@mail.gmail.com> (raw)
In-Reply-To: <m3ejgi5mvw.fsf@localhost.localdomain>
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 <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?
>
>
>
>
next prev parent reply other threads:[~2007-09-29 0:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-29 0:36 Ian Lance Taylor
2007-09-29 0:41 ` Daniel Berlin [this message]
2007-09-29 1:27 ` Ian Lance Taylor
2007-09-29 2:00 ` Daniel Berlin
2007-09-29 5:22 ` NightStrike
2007-09-29 5:26 ` Daniel Berlin
[not found] ` <b609cb3b0709290503l41bd9adcifdde549e2a895b4f@mail.gmail.com>
2007-09-29 14:02 ` Daniel Berlin
2007-09-30 5:09 ` NightStrike
2007-09-30 20:22 ` Daniel Berlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4aca3dc20709281741j346345bs8fd4ad1fb9967e99@mail.gmail.com \
--to=dberlin@dberlin.org \
--cc=iant@google.com \
--cc=nightstrike@gmail.com \
--cc=overseers@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).