You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Steven H @ orcon" <sm...@orcon.net.nz> on 2005/06/15 02:23:42 UTC

svnserve security question

Hey all, 

I just have a question regarding exposing svnserve to the wild (as in
internet) has anybody done it?

Im just trying to gauge whether its mature enough for that, maybe the fact
that svn's own server doesn’t do it should be enough for me.

---------------------------------------------------------------------------

Steven Higgan - 3rd Year B.I.T. Otago Polytechnic, Dunedin New Zealand 
.net geek


-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.7.2 - Release Date: 14/06/2005
 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: svnserve security question

Posted by "Steven H @ orcon" <sm...@orcon.net.nz>.
Thank you very much for your reply, my boss will be happy too.

---------------------------------------------------------------------------

Steven Higgan - 3rd Year B.I.T. Otago Polytechnic, Dunedin New Zealand 
.net geek


-----Original Message-----
From: kfogel@newton.ch.collab.net [mailto:kfogel@newton.ch.collab.net] On
Behalf Of kfogel@collab.net
Sent: Wednesday, 15 June 2005 5:53 p.m.
To: Steven H @ orcon
Cc: 'Subversion Users List'
Subject: Re: svnserve security question

"Steven H @ orcon" <sm...@orcon.net.nz> writes:
> I just have a question regarding exposing svnserve to the wild (as in
> internet) has anybody done it?

Yes, it's done all the time.

> Im just trying to gauge whether its mature enough for that, maybe the fact
> that svn's own server doesn’t do it should be enough for me.

No, the reasons svn.collab.net offers only http:// access are mainly
historical.  We offered http:// before there was svn://, and even now
that it's possible to do both, we just don't want the hassle of
maintaining two repository access methods.  However, security and
maturity were not factors in this decision -- were they the sole
concerns, we'd happily offer svn:// access too and still sleep soundly
at night.

Best,
-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org



-- 
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.7.2 - Release Date: 14/06/2005
 

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.7.2 - Release Date: 14/06/2005
 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svnserve security question

Posted by kf...@collab.net.
"Steven H @ orcon" <sm...@orcon.net.nz> writes:
> I just have a question regarding exposing svnserve to the wild (as in
> internet) has anybody done it?

Yes, it's done all the time.

> Im just trying to gauge whether its mature enough for that, maybe the fact
> that svn's own server doesn’t do it should be enough for me.

No, the reasons svn.collab.net offers only http:// access are mainly
historical.  We offered http:// before there was svn://, and even now
that it's possible to do both, we just don't want the hassle of
maintaining two repository access methods.  However, security and
maturity were not factors in this decision -- were they the sole
concerns, we'd happily offer svn:// access too and still sleep soundly
at night.

Best,
-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org