Ed MacDonald wrote:
>>This doesn't actually happen quite like that in Subversion, because the
>>actual scenario is
>>
>> svn --> ssh --> svnserve --> Repository --> FileSystem
>>
>>That is, you use ssh for tunneling svnserve's socket connection, not for
>>login onto the server. In fact, CVS does things like that, too.
>>
>>Of course, if you do allow users to log onto the server, whether via SSH
>>or some other mechanism, neither SVN or CVS can do anything to protect
>>your data.
>>
>>
>
>I don't believe that svnserve uses sockets at all in this scenario - just
>stdin/stdout. In which case it is pretty much as Pete so colourfully said,
>you can have your way with the DB since the svnserve process is running as
>the user and must be given read/write on the repo.
>
>
You can restrict the SSH session to only allow the user to execute
svnserve, and you can make svnserve setuid (not to root, of course). The
user can still get to the repository by cracking svnserve, but that's no
different than in scenarion (B).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 29 04:23:19 2004