Re: AW: svn:external question

Hi Felix,

On Friday, November 26, 2004, Felix Gilcher wrote:

> this is quite easily realized. For the less paranoid: give all
> developers read-only access to all repositories. The can use them as
> externals now. Give them read-write access to those repositories
> that they really need to work on. For the more paranoid: every time
> a user needs a certain repository as external, grant him access.
> This is more work to administrate but helps you to keep track of who
> is accessing which repository. Mod_authz_svn even allows you to
> restrict users to certain branches/tags or even directories.

I will try... :)

> The svn:externals definitions does not imply any permission to read
> the repository that it points to, which is a good thing. Remember
> that this property is set by the user and not by the admin, even
> though it is tracked by svn. Thus, if it would imply a read
> permission you could use it to give yourself read access to a
> repository that you're not even allowed to look at just by setting
> it as svn:externals. Permissions are only granted by the admin in
> the apropriate config file which depends on the access-method you
> use.

that's right and thank you for your explanation.

-- 
Regards,
Enrico Straube
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org