Hi Steven! > 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
Expression "adding *=" is not correct in the authz-windows file. If you want to deny access to any user please use the standard group Everyone. > 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? Please could you provide more details about the problem with using SIDs? Thank you! On Thu, Jan 29, 2009 at 3:14 AM, Steven <steven.be...@gmail.com> wrote: > > 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? > -- Olga Dolidze VisualSVN Support
