>> >Have you tried this yet?
>> >
>> >http://svnbook.red-bean.com/en/1.1/ch06s04.html#svn-ch-6-sect-4.4.3
>>
>> Yes; this disables authorisation completely, which isn't acceptable
>> for me.
>> I need good access control, but I'm willing to live with a
>tiny bit of
>> leaked meta-information in the logs.
>
>Actually, it does pretty much exactly what you want. It
>disables the extra path-based checks that Subversion does.
>Operations like checkout and commit already hit those paths,
>so all of the checks still occur and you still get enforcement
>of things like making paths read-only, and certain paths
>not-readable. What you lose, is that operations like svn log
>can potentially show log entries for items the user is not
>authorized to see. But even then, only if the user run's log
>on say the root of the repository.
I see you came across this problem with 1.1.1 (judging by the archives).
Unfortunately I can't get this option to work very well for me.
Some timings for svn log (repeated three times on an unloaded server):
No SVNAuthPath directive: 36.9, 30.8, 31.0
SVNAuthPath off : 18.4, 23.9, 2:34 (!)
No directive, patched : 4.4, 3.9, 4.4
No idea what caused the glitch for the 2:34 time. Note - this is svn 1.2
with
apache 2.0.52, ldap authentication. Are these timings what you'd expect?
Dave
>
>Mark
>
>
>_______________________________________________________________
>______________
>Scanned for SoftLanding Systems, Inc. by IBM Email Security
>Management Services powered by MessageLabs.
>_______________________________________________________________
>______________
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jun 9 15:55:57 2005