>Additionally, the Subversion development team has announced file://
>protocol should not be considered for production environments.
Reread OP then, I'm trying to get away from using a file:// URL, using
PSexec to execute svnserver.
On Tue, Mar 23, 2010 at 11:14 PM, Andy Levy wrote:
> On Tue, Mar 23, 2010 at 15:46, yary wrote:
>>>You should stop doing so immediately and set up a proper server. Any user
>>>with direct file:-protocol access to the repository can access any part of it
>>>(bypassing any path-based security you'v
On Tue, Mar 23, 2010 at 15:46, yary wrote:
>>You should stop doing so immediately and set up a proper server. Any user
>>with direct file:-protocol access to the repository can access any part of it
>>(bypassing any path-based security you've put in place) and can even delete
>>the entire reposito
>You should stop doing so immediately and set up a proper server. Any user
>with direct file:-protocol access to the repository can access any part of it
>(bypassing any path-based security you've put in place) and can even delete
>the entire repository (accidentally or intentionally).
What you ar
On Mar 23, 2010, at 12:40, yary wrote:
> I'm using Subversion in a windows shop. We have a FSFS repository that
> we're accessing via XP's filesharing (file: URLs with UNC paths).
You should stop doing so immediately and set up a proper server. Any user with
direct file:-protocol access to the
Hello,
I'm using Subversion in a windows shop. We have a FSFS repository that
we're accessing via XP's filesharing (file: URLs with UNC paths).
Company policy won't allow us to install ssh/sshd, or to run any new
services such as apache or svnserver as a deamon.
We have PSexec installed on our sv
