Sebastian Goebel wrote: > Dear all, > > > I am new subscriber of this list. My name ist Sebastian Goebel, and I am > software developer, mostly open source internet applications. > > We are sucessfully using Trac (+Subversion) as project management tool sice > over 2 years, so my respect to the developer team! > > > Now I was running into a special problem: > > Our svn repos are readable by public, as the whole trac area too. For some > customer development, I use branches, which are hidden from public acces by > svn pathbased authentication. For the trac repo browser I did it by setting > http auth for those paths, like such rule: > > <Directory BRANCHES/hidden_project> > AuthType Basic > (...) > </Directory> > > But I found that public users can access files by using changeset numbers, > and than the download link at bottom of page to get the whole file. > > Is there some way, or have someone idea for approach to safely protect an > whole branch from public access in trac? > > > Look up Subversion's authz system, it does this, and Trac supports enforcing those permissions in the browser.
--Noah
signature.asc
Description: OpenPGP digital signature
