From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Upcoming Infra maintenance/downtimes: anon{cvs,svn,git}, archives, bouncer, overlays
Date: Fri, 18 Jan 2008 14:49:30 -0800 [thread overview]
Message-ID: <20080118224930.GK5504@curie-int.orbis-terrarum.net> (raw)
In-Reply-To: <9e0cf0bf0801181426x5309e4dfk6f3d9641a1f965b9@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1688 bytes --]
On Sat, Jan 19, 2008 at 12:26:44AM +0200, Alon Bar-Lev wrote:
> On 1/18/08, Mike Frysinger <vapier@gentoo.org> wrote:
> > On Thursday 17 January 2008, Robin H. Johnson wrote:
> > > anonvcs.gentoo.org: anoncvs, anonsvn, anongit
> > > - Anonymous SVN is changing from http:// to svn:// [1]
> > > overlays.gentoo.org [3]:
> > > - Anonymous SVN is changing from http:// to svn://
> > i'd point out that http:// syncing is usable from behind firewalls while
> > svn:// is not ... while this does not affect me personally, it's something to
> > keep in mind.
> > -mike
> Just wanted to note this too... I am one of the affected ones...
> I think that it is very important to have http, and even https for
> formal resources.
> git://, svn://, rsync:// or ssh+X:// are inaccessible for a large
> group of users.
My core concern with the SVN http://, was the crappy performance it
provided compared to svn://. The main rsync tree has never been
available for iterative syncing via http://, just had tarball snapshots
and deltas instead.
> Also using none secured protocols, exposes users to man-in-the-middle attacks.
The existing http:// had this problem already, it's not a new one.
git:// and svn:// do both have patches around adding support for adding
TLS. This however just adds overhead, I really need to finish the
tree-signing work I was doing, as that protects the content better (MITM
is still possible on SSL without it, just a lot harder as an attacker
has to deal with the SSL stream first).
--
Robin Hugh Johnson
Gentoo Linux Developer & Infra Guy
E-Mail : robbat2@gentoo.org
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
[-- Attachment #2: Type: application/pgp-signature, Size: 329 bytes --]
next prev parent reply other threads:[~2008-01-18 22:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 21:47 [gentoo-dev] Upcoming Infra maintenance/downtimes: anon{cvs,svn,git}, archives, bouncer, overlays Robin H. Johnson
2008-01-18 8:37 ` Fabian Groffen
2008-01-18 9:21 ` Robin H. Johnson
2008-01-18 9:46 ` Fabian Groffen
2008-01-18 11:32 ` Robin H. Johnson
2008-01-18 11:39 ` Fabian Groffen
2008-01-18 11:37 ` Mike Frysinger
2008-01-18 22:26 ` Alon Bar-Lev
2008-01-18 22:49 ` Robin H. Johnson [this message]
2008-01-18 23:01 ` Alon Bar-Lev
2008-01-18 23:06 ` Arfrever Frehtes Taifersar Arahesis
2008-01-18 23:28 ` Alon Bar-Lev
2008-01-19 2:36 ` Robin H. Johnson
2008-01-19 20:50 ` Mike Frysinger
2008-01-19 20:56 ` Alon Bar-Lev
2008-01-19 21:27 ` Fabian Groffen
2008-01-21 18:34 ` Michael Haubenwallner
2008-01-18 17:41 ` [gentoo-dev] " Christian Faulhammer
2008-01-18 22:13 ` Robin H. Johnson
2008-01-19 16:36 ` Petteri Räty
2008-01-20 12:56 ` [gentoo-dev] " Thomas Anderson
2008-01-21 13:08 ` Robin H. Johnson
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=20080118224930.GK5504@curie-int.orbis-terrarum.net \
--to=robbat2@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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