[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Subversion security design

From: Jonathan S. Shapiro <shap_at_eros-os.org>
Date: 2000-06-28 16:36:51 CEST

> The fact that people haven't [added different access control
> strategies] suggests that it's not as important as we're often
> led to believe.

That may be true.

Another possibility is that CVS isn't and never has been truly distributed
(remoted yes, distributed no), and that there is no need for a distributed
access control mechanism in a non-distributed system. In fact, many people
seem to use cvs-acls, which is sufficient in the non-distributed case.

I'm not suggesting that anybody commit huge energy to building a distributed
solution. I'm merely suggesting that we should understand the requirements
lest we accidentaly design an interface or protocol that precludes solving
this later.

shap
Received on Sat Oct 21 14:36:05 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.