[cvsacl-users] cvsacl 1.2.0 for cvs 1.11.17 doesn't appear to work

[Mortensen, M. <mar...@th...>]

Alright I was told by our CM team that we had to upgrade to CVS 1.11.17 to
fix some security issues.  We are currently using CVS 1.11.5 with cvsacl
1.1.0 with no problems.  CVSACL works great and does what we want. I
downloaded the new patch and ran into a build issue that was noted by Alex
on this list entitled "cvs-1.11.17-cvsacl-1.2.0-patched compile error".
After fixing the acl.c file as per the email the server is able to compile
and correctly reports the version.  I created a brand new respository to
test with but now the cvsacl doesn't appear to be working.  We are building
on Solaris.  Here is what we have

/TEST2/
  |
  |
  +--CVSROOT/
  |
  |
  +--projectA/
       |
       |
       +--src/...

Inside of CVSROOT is the access file used by cvsacl and contains

# CVS ACL definitions file. DO NOT EDIT MANUALLY
d:ALL:ALL:mmortens!p,ALL!a:
d:projectA:ALL:testuser!n:

So if the "testuser" logs into CVS via a pserver connect the user should not
be able to checkout the projectA module.  However, the testuser can.  I
backed out the binaries to older cvs/cvsacl (1.11.5 w/cvsacl 1.1.0) patch
version and the correct behaviour is encounted and the testuser can not
checkout the projectA module.

Am I missing something simple here?

-Mark


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________