[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [SAGE] Subversion, passwords and ACLs
On Jan 22, 2007, at 1:06 PM, Paul Lussier wrote:
> Neil Watson <sage@watson-wilson.ca> writes:
>
>> Suppose I have a Subversion repository:
>>
>> /trunk/
>> /branches/dev
>> /branches/qa
>>
>> I want to be able to limit users to certain directories. John should
>> only be able to access branches/qa. Jane should only be able to
>> access
>> branches/dev.
>>
>> I can accomplish this using Subversion's authz-db files. Using this
>> method users contact a running Subversion daemon. Their
>> credentials are
>> stored in a password-db file. I do not like that this file is plain
>> text. I also do not like that this does not give the user's a
>> chance to
>> change their passwords.
>>
>> Is there a way to control directory access inside a repository while
>> still using UNIX shell accounts for logins?
>
You might also want to take a look at
tools/hook-scripts/commit-access-control.pl.
which lets you use a simple configuration file to control who has
read-only vs. commit access to parts of your repository if you set it
up as a pre-commit hook script. There's also, I think, a python
equivalent. Since the script works in the repository it's agnostic
about whether access is HTTP or svnserver or file:.
--Peter
--
Peter Burkholder
email: pburkholder@pobox.com; AIM: peterbtech; Skype: pburkholder
phone: +1-303-497-2663 (work) or +1-303-359-4842 (cell)
http://www.pburkholder.com
PGP Key Fingerprint: B473 C1CF D8B0 7941 8F95 7627 4785 86C9 F1F4 81DC
PGP Key URL: http://pburkholder.com/gpg.txt