Do you need to restrict READ access to the branch or tag, or do you
simply want to restrict COMMIT access.
If you just want to restrict commit access, you can use a pre-commit
hook to kill a commit transaction if the user who doesn't have
permission attempts to change a tag or branch.
There is a
> Do you need to restrict READ access to the branch or tag, or do you
> simply want to restrict COMMIT access.
Thanks for the response. We need both, but restricting read access is
the main concern at the moment. So far, I only know of AuthUserFile
for controlling read access.
> If you just wan
> > Do you need to restrict READ access to the branch or tag, or do you
> > simply want to restrict COMMIT access.
>
> Thanks for the response. We need both, but restricting read access is
> the main concern at the moment. So far, I only know of AuthUserFile
> for controlling read access.
>
> >
On Wed, Oct 13, 2010 at 2:12 PM, Shaun Pinney
wrote:
>> Do you need to restrict READ access to the branch or tag, or do you
>> simply want to restrict COMMIT access.
>
> Thanks for the response. We need both, but restricting read access is
> the main concern at the moment. So far, I only know of
> The usual issue is making sure people outside the project are
> prevented from reading the code. You might not want people in your
> project making changes on tags and branches, but there usually isn't a
> security issue if they see the code on the branches and tags.
Our issue is handling multip
On Wed, Oct 13, 2010 at 3:42 PM, Shaun Pinney
wrote:
>> The usual issue is making sure people outside the project are
>> prevented from reading the code. You might not want people in your
>> project making changes on tags and branches, but there usually isn't a
>> security issue if they see the co
- Original Message
> From: Shaun Pinney
> > The usual issue is making sure people outside the project are
> > prevented from reading the code. You might not want people in your
> > project making changes on tags and branches, but there usually isn't a
> > security issue if they see th
On Wed, Oct 13, 2010 at 3:59 PM, BRM wrote:
> And that's why you use LDAP or another alternative authentication method.
> BTW, Subversion does support groups as part of the path-based authentication.
> I don't know how that interacts with LDAP if at all, but that might be
> something
> to investi
> > Our issue is handling multiple companies doing development on the same
> > project. Various restrictions (e.g. licensing) prevent us from sharing
> > all project files with everyone involved. It's a tricky use case. We
> > also have additional considerations which require us to control proje
> > When your development team gets bigger than a dozen people, you start
> > > having people come and go all the time. That makes it difficult to
> > > keep the httpd configuration up to date. It just becomes easier if
> > > this becomes more automated. Or at least someone else's problem when
> If you need to control access to the code you can do things such as:
> - only allow the developers that need access access to the whole project
Yep, we do this. There are still some restricted areas in some projects
though.
> - setup a secondary tags namespace for special binary only informati
> > If you need to control access to the code you can do things such as:
> > - only allow the developers that need access access to the whole project
>
> Yep, we do this. There are still some restricted areas in some projects
> though.
>
> > - setup a secondary tags namespace for special binary
12 matches
Mail list logo
