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

RE: SVN Security

From: Edward Bosco <ebosco_at_prologic-inc.com>
Date: 2006-04-14 20:18:11 CEST

-----Original Message-----
From: Nico Kadel-Garcia [mailto:nkadel@comcast.net]
Sent: Friday, April 14, 2006 1:22 PM
To: Edward Bosco; Timo Wendt; david.anderson@calixo.net
Cc: users@subversion.tigris.org
Subject: Re: SVN Security

Edward Bosco wrote:
> Does Subversion plus some other OSS packages permit per-item access
> control?

Subversion plus being able to write the svnperms.conf file should, as
well
as HTTPS based access control should. But I like the
svnperms.py/svnperms.conf setup better: it has a finer grain of
resolution
with its distinct "add,delete,update" options. The format is very
similar to
that of the classic svnserve.conf, so it should be an easy switch from
one
to the other.

-----Original Message Above-----

Appreciate the reply, Nico.

It's a harder problem than I originally considered. The .svn/text-base/
directory contains plaintext versions of the original files.

If I don't wish users to be able to see some aspect of all the files
within the directory, irregardless of the user's nominal privileges,
We'd need to protect that .svn directory.

Would the Python scripts prevent users from seeing filenames or file
contents they're forbidden to view within their working directories
within their client computers?

In any case, A Happy Easter to you and all.
Ed.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 14 20:22:22 2006

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

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