Re: a few nits setting up svn...

Perry E. Metzger wrote:

>Luis Malheiro <luis.malheiro@rerum.com.br> writes:
>
>
>>Well, if I can't use https://, I would use svn:// tunneled through a
>>SSH connection... Am I missing something on this approach?
>>
>>
>Not much. That's what I'm trying to use.
>
>However, right now that requires that I leave the repository group
>writable for all the users. They might accidently damage it as a
>result.
>
>I'd rather make the repository owned by a particular account or group
>and have a suid or sgid executable deal with preventing accidents.
>
>Perry
>
>

svn:// tunneled through ssh is NOT what you are trying to use! You are
trying to use svn+ssh://, which should probably really be called
file+ssh://. svn+ssh:// uses direct file access, svn:// does not.

Using svnserve via ssh will redirect ports from a local machine to the
remote machine, over the encrypted link. THIS IS NOT AT ALL THE SAME AS
svn+ssh://!

-- 
Brian Mathis
http://directedge.com/b/