[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: bad access methods (was: 100% repeatable repo wedging)

From: Jarod Wilson <jarod_at_voicebox.com>
Date: 2004-03-04 22:17:43 CET

> -----Original Message-----
> From: Matthew Gregan [mailto:kinetik@orcon.net.nz]

> > > This brings me to the question of why are you using
> > > svn+ssh? Out of
> > > the 4 access methods you have to choose from, you've
> > > chosen (IMO),
> > > the 3rd most desirable one. They are, in order of desireability:
> > > 1. http
> > > 2. svnserve daemon
> > > 3. svn+ssh
> > > 4. file
>
> > That's easy. Security. svnserve sans ssh isn't secure. https is, or
> > can be, anyway, but it's not always an option.
>
> So spend an extra five minutes during the initial svnserve
> configuration and wrap svnserve up with stunnel. I can write
> up and post some documentation on how to do this if anybody
> would find it useful.

Not particularly useful in my particular instance, since I'd rather have
unique logins. Oh! Wait! I'm now remembering that svnserve.conf file...
I *can* have unique logins with svnserve. Oh yeah (sorry, still very
green to Subversion). But the passwords sit in a file unencrypted. Icky.
And I have to maintain multiple user/password databases, rather than
using the system one.

However, I'd still be intrigued to hear how to wrap svnserve in stunnel.

-- 
Jarod C. Wilson, RHCE
System Administrator
VoiceBox Technologies
jarod@voicebox.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 4 22:16:39 2004

This is an archived mail posted to the Subversion Users mailing list.