You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Bicking, David (HHoldings, IT)" <Da...@thehartford.com> on 2007/10/12 13:35:41 UTC
Security and repository properties
Perhaps I missed it in the book, but I don't see any means to secure
repository properties. The one two cases I see where this is important
is the "needs lock" and "externals" properties. I can see where certain
maverick developers might decide "this is only for the stupid
programmers, not me" (yeah, I work in a corporate environment, and have
known people like this). Is there a way to secure certain property
types? If not, is there a chance it would be considered as an
enhancement?
I suspect the (perfectly reasonable) answer will be "use a pre-commit
script". If so, do any of you happen to know a canned one I can lift?
--
David
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Security and repository properties
Posted by "Bicking, David (HHoldings, IT)" <Da...@thehartford.com>.
> -----Original Message-----
> From: Blair Zajac [mailto:blair@orcaware.com]
>
> I could see people deleting svn:needs-lock, but removing an
> svn:externals would break a build, so why would people remove
> that one?
"Gee, this external is pointing to r35, but I need it to use HEAD..."
Imagine discovering this change a month later, after making two or three
release tags on the project.
>
> >
> > I suspect the (perfectly reasonable) answer will be "use a
> pre-commit
> > script". If so, do any of you happen to know a canned one
> I can lift?
>
> I'm not aware of any implementations of such a hook script.
It was worth a shot.
>
> Regards,
> Blair
>
--
David
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Security and repository properties
Posted by Blair Zajac <bl...@orcaware.com>.
On Oct 12, 2007, at 9:35 AM, Bicking, David (HHoldings, IT) wrote:
> Perhaps I missed it in the book, but I don't see any means to secure
> repository properties. The one two cases I see where this is
> important
> is the "needs lock" and "externals" properties. I can see where
> certain
> maverick developers might decide "this is only for the stupid
> programmers, not me" (yeah, I work in a corporate environment, and
> have
> known people like this). Is there a way to secure certain property
> types? If not, is there a chance it would be considered as an
> enhancement?
Only by the hook scripts. I don't think this would make it into svn
core itself and we would leave it to be implemented by a hook script.
I could see people deleting svn:needs-lock, but removing an
svn:externals would break a build, so why would people remove that one?
>
> I suspect the (perfectly reasonable) answer will be "use a pre-commit
> script". If so, do any of you happen to know a canned one I can lift?
I'm not aware of any implementations of such a hook script.
Regards,
Blair
--
Blair Zajac, Ph.D.
<bl...@orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org