In VisualSVN server in windows authentication the authz-windows don't
seem to be able to handle *= on sub paths

ie, in a standard authz you can restrict a subpath by simply adding *=
to remove rights from anyone, then selectively add people back in

[myrepo:/trunk/app/secured.file]
* =
poweruser = rw

but with the authz-windows file the gui still lists any users with
access higher up the path has still having access to the secured file

Also - the use of SIDs - while useful in certain circumstances - is a
pain. the idea of a non standard authz in general is bad - perhaps it
use could be made optional?

Reply via email to