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

RE: File access control

From: Cooke, Mark <mark.cooke_at_siemens.com>
Date: Thu, 29 Sep 2011 07:31:50 +0100

> -----Original Message-----
> From: Grant [mailto:emailgrant_at_gmail.com]
> Sent: 29 September 2011 03:42
> To: users_at_subversion.apache.org
> Subject: File access control
> I see that subversion supports path-based authorization:
> http://svnbook.red-bean.com/en/1.5/svn.serverconfig.pathbasedauthz.html
> Is there a way to do file-based authorization? Or maybe some sort of
> trickery to mimic file-based authorization? If not, can anyone think
> of a way to allow read/write access to only certain files in a working
> system? I could use chmod/chown but the files to which access is
> allowed will be changing pretty frequently so it would be nice to have
> accessible files defined in a list as part of the version control
> system, file transport mechanism, or anything else.
I believe that the short answer is 'no'. There are strategies that could help depending on why you need the restrictions. However, chmod/chown is not one of them as it is not easy (nor recommended) to work out which objects in the fsfs data correspond to which files in the repo and each new revision will generate new fsfs elements (unless you use packing...)

Can you sketch out why you think you need to protect specific files?

~ mark c
Received on 2011-09-29 08:32:34 CEST

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