From the svn bool.
" When running over a tunnel, authorization is primarily controlled by
operating system permissions to the repository's database files; it's
very much the same as if Harry were accessing the repository directly
via a file:// URL."
That says to me that the *nix user that is logged in needs rw access to
the repository files in order to access the repository. In other words,
they would have access to the files within the shell. I think that is
something the OP didn't like.
BOb
> -----Original Message-----
> From: Paul Koning [mailto:Paul_Koning_at_dell.com]
> Sent: Friday, December 19, 2008 12:44 PM
> To: Bob Archer
> Cc: bobdole1_at_web.de; users_at_subversion.tigris.org
> Subject: RE: access svn securely from the internet via sasl or ssh
>
> >>>>> "Bob" == Bob Archer <Bob.Archer_at_amsi.com> writes:
>
> Bob> Svn protocol isn't really secure. It is meant for intranets. SSH
> Bob> tunnel makes it secure but you said you don't want to give you
> Bob> users rw accsess to the repository. So, I think that only leaves
> Bob> moving to https via Apache.
>
> You can certainly deny read-write access when using svn+ssh.
>
> paul
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=987668
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-19 18:52:07 CET