Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
I absolutely agree with you on how much this problem/bug is annoying. (I was about to file a bug ticket in mantis, but since the network admins didn't even complain about having to change/loose resitrictons, I let it alone) But the problem is a bit different than you might think. Currently this is what's needed: - The account you have cvsnt running on (usually SYSTEM) must have "List Folder" permission from the CVSROOT repository folder up to the partition root, and read access to CVSROOT/modules. Note that "Travese Folder" is a different permission which almost all accounts are automatically and globally granted because of the "Bypass traverse checking", even on Windows 2003 server. - The users which access CVS must have the same "List Folder" permission on the repository up to its partition root; same for the CVS Temp directory. Tony, I'm positive this is a recent bug; AFAIR 2.0.41 wasn't affected. Maybe some code rework using a recursive function? Flávio -----Original Message----- However, it bothers me that I must grant read and list access to all the directories (from the root of the drive volume) all the way down to the CVS repository's directory. This seems wrong to me. I don't want my users to have the ability to traverse these directories. Why can't the CVSNT server process use its rights (as SYSTEM, I assume) to traverse the intervening directories (from the volume's root down to the CVS repository's directory) and THEN examine the user's ACL to see if they have rights to the module they are trying to access? (In a sense, isn't this the same as the "virtualized" path to the repository's root that Tony implemented some years ago?) Donald T. Gates