I completely agree that it will be best if there is only one ".svn"
directory, because we can easily change its security policy to suit each
one's needs.
It seems that SVN 1.7 will resolve my current security concerns, so I
guess I'll have to wait for its stable release.
Until then I'll ei
> -Original Message-
> From: Ivan Zahariev [mailto:rrdt...@famzah.net]
> Sent: vrijdag 15 januari 2010 7:46
> To: David Glasser
> Cc: dev@subversion.apache.org
> Subject: Re: More strict file permissions for the administrative ".svn"
> directorie
You can always "chgrp $COMMON_GROUP .svn" directories and make all users
have this $COMMON_GROUP as their Group ID. This way they can still
share the ".svn" directories and still "others" (like the Web server)
won't be able to go in there.
You are right about the problem if someone chmod()'
On Tue, Jan 12, 2010 at 10:40 AM, Ivan Zahariev wrote:
> Hi devs,
>
> I've first discussed this at the "users" list and there was no big
> interest but also no negative feedback there. Therefore I'm suggesting
> this to you now:
>
> Would you make the ".svn" directories not accessible by "others"
Hi devs,
I've first discussed this at the "users" list and there was no big
interest but also no negative feedback there. Therefore I'm suggesting
this to you now:
Would you make the ".svn" directories not accessible by "others" (thus
being accessible only by the "owner" and "group") ?
You can r
5 matches
Mail list logo
