cvsacl-users Mailing List for CVS Access Control List Extension (Page 3)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

don`t work?

-- 
Sincerely yours,
Kluchnikov A.

Thanks,

Best Regards,
Paola

sbaris wrote:

> System users in the server can make changes locally on CVSROOT/access 
> file if file system
> permissons are write enabled. You can give only read file system 
> permisson to CVSROOT/access file,
> so they cannot change the file locally on server.
>  
> cvsacl patch only works over pserver connection.
> Local users using local cvs command on server does not affected from 
> cvsal permissions,
> so you may restrict users from logging in to server via telnet or SSH.
>  
> Regards,
> sb...@us... <mailto:sb...@us...>
>  
>  
>  
> ----- Original Message -----
>
>     From: Paola Attadio <mailto:pao...@or...>
>     To: cvs...@li...
>     <mailto:cvs...@li...>
>     Sent: Wednesday, November 24, 2004 4:13 PM
>     Subject: [cvsacl-users] ACL Administrator
>
>     All,
>
>     I have CVS patched with CVSACL, It works perfectly, but I don't
>     understand some things.
>
>     My CVS use pserver, for this reason I created passwd and group
>     files in CVSROOT directory. Then, the ACL rules are based in cvs
>     users and groups. I choose a cvs user as acl admin (acladmin), in
>     others words, I execute the next sentence locally to the CVS server:
>          $cvs racl  acladmin:p -r ALL -d ALL
>
>     After that, I set other permissions to the others cvs users and
>     groups.
>
>     Everything works perfectly, the users use a WinCVS client and They
>     just only make the operations that the ACL rules allow. But I
>     don't understand the meaning of the acl admin, because a system
>     user in the server makes changes in the rules without being an acl
>     admin.
>
>     Am I doing something wrong?
>
>     Thanks in advance,
>
>     Paola
>
>
>
>

CVSACL-1.2.2 is uploaded to sf.net.

Updated for cvs-1.11.18
Fixed open bugs: 1064405,1025575

Regards,

sb...@us...
http://cvsacl.sourceforge.net

System users in the server can make changes locally on CVSROOT/access =
file if file system
permissons are write enabled. You can give only read file system =
permisson to CVSROOT/access file,
so they cannot change the file locally on server.

cvsacl patch only works over pserver connection.
Local users using local cvs command on server does not affected from =
cvsal permissions,
so you may restrict users from logging in to server via telnet or SSH.

Regards,
sb...@us...
=20

----- Original Message -----=20
  From: Paola Attadio=20
  To: cvs...@li...=20
  Sent: Wednesday, November 24, 2004 4:13 PM
  Subject: [cvsacl-users] ACL Administrator

  All,

  I have CVS patched with CVSACL, It works perfectly, but I don't =
understand some things.=20

  My CVS use pserver, for this reason I created passwd and group files =
in CVSROOT directory. Then, the ACL rules are based in cvs users and =
groups. I choose a cvs user as acl admin (acladmin), in others words, I =
execute the next sentence locally to the CVS server:
       $cvs racl  acladmin:p -r ALL -d ALL

  After that, I set other permissions to the others cvs users and =
groups.

  Everything works perfectly, the users use a WinCVS client and They =
just only make the operations that the ACL rules allow. But I don't =
understand the meaning of the acl admin, because a system user in the =
server makes changes in the rules without being an acl admin.

  Am I doing something wrong?

  Thanks in advance,

  Paola

All,

I have CVS patched with CVSACL, It works perfectly, but I don't 
understand some things.

My CVS use pserver, for this reason I created passwd and group files in 
CVSROOT directory. Then, the ACL rules are based in cvs users and 
groups. I choose a cvs user as acl admin (acladmin), in others words, I 
execute the next sentence locally to the CVS server:
     $cvs racl  acladmin:p -r ALL -d ALL

After that, I set other permissions to the others cvs users and groups.

Everything works perfectly, the users use a WinCVS client and They just 
only make the operations that the ACL rules allow. But I don't 
understand the meaning of the acl admin, because a system user in the 
server makes changes in the rules without being an acl admin.

Am I doing something wrong?

Thanks in advance,

Paola

The acl code as distributed always gives read permission to anyone who 
has write permission, and for our purpose, we needed read permission to 
be unrelated to write permission. I changed a few lines of code in the 
valid_permissions() function to do this, and in the aclconfig set the 
default permissions to n, and now I've been trying to figure out why 
things aren't working. As I have examined the code, I found some parts 
that appear to be problems in acl.c

=== access_allowed(): Use of accessfilecount: ===

The routine contains a loop

    for (accessfilecount; accessfilecount >= 0 && !oneaccessfile; 
accessfilecount--)

It looks like there is code missing here, and either the statement 
should assign an initial value to accessfilecount.

    for (accessfilecount = ...... ;

or the variable should get an initial value earlier. Before this "for" 
statement, accessfilecount is assigned an initial value only if the file 
parameter to this routine is non-null. If file is null, you enter the 
loop with a random number in accessfilecount.

I changed the code to give accessfilecount an initial value of 0. Seems ok.

==== access_allowed(): retval overwritten ====

One of the main loops of this routine is a while statement that get 
calls getline() to get a line from the access file and process it. In 
this loop, it assigns retval a value of 1 or 0 depending upon whether 
access to the file is allowed or not. The problem is that each iteration 
of the loop overwrites the retval from the previous iteration, which 
means that the only line in the access file that counts is last line.

In my case, the access file looks like this and I am wrk.

d:ALL:ALL:cvsca!p:
d:ALL:ALL:configwriter!wc:
d:ALL:ALL:ALL!n,wrk!p:
d:ALL:ALL:jjohnson!p:

If I try to list the permissions on a directory (cvs -d 
/data/local/cvsca racl -l -d Practice) permission is denied. As the code 
iterates thorugh the file, retval is set to 0 for the first 2 lines, set 
to 1 for the 3rd line, and set to 0 again for the 4th line, and which 
point the loop ends and I am denied access.

I changed the code so it terminates the main while loop when retval is 
nonzero, and that seems to be working ok.

    while (getline (&line, &line_allocated, accessfp) >= 0 && retval == 0)

==== Can't set permissions ===

I have a directory Practice containing a file Test3.txt. I wanted to 
give a user "configwriter" read permission on this, and so I tried the 
following command and it didn't work.

[jjohnson@foo jjohnson]$ cvs -d /data/local/cvsca racl configwriter:+r 
-f Practice/Test3.txt
cvs racl: Practice/Test3.txt user is not given any permissions to remove/add

Am I doing something incorrectly? Tracing through the code, I don't see 
how it will ever work, so I am certainly missing something. The command 
invokes acl_fileproc, which in turn invokes access_allowed, then 
make_perm. Make_perm depends on having some line, I think the line for 
the user configwriter, returned by access_allowed. However, 
access_allowed will never return the line because it contains a 
comparison "strcmp (dirs[x], part_object)", where the values are:

  dirs[0]  = Practice
  dirs[1]  = Practice/Test3.txt
   part_object = ALL

The comparsion always fails. Should the statment actually be:

    if (strcmp("ALL", part_object) == 0 || strcmp (dirs[x], part_object) 
== 0)

Trying that makes the code fail in other ways, so I am surely twisted 
around and confused. Can anyone help?

Willard

Yesterday I was able to manipulate the acls for my cvs archive without 
any problem. Today, if I try to add a user

   cvs -d /path/to/archive racl someuser:p -d ALL -r ALL

I get "cvs [racl aborted]: You do not have admin rights on '.'" I can't 
list permissions on directories or file.
Something changed, but I haven't figured out what. Someone asked a 
similar question back in August, but there's no reply in the list archive.

The access file contains the line

    d:ALL:ALL:ALL!n,wk!p:

where wk is my id.

I am using cvsacl-1.2.1 on cvs-1.11.17. I put some debug logging into 
the valid_perm() function in acl.c When I try to change the user 
permissions, the part_perms parameter is null, so it takes the default 
permission, which I set to n.

Thanks for any help.

Willard

I haven't used cvsacl for long (bout 10 days) but its far more
simpler than managing access control using unix permissions
( even with pserver auth, and still there are things one just can't do).
As I said its not been long but I think Iam going to stick with it
for a long time. I have had no problems ( but have solved quite
a few using it)
Dev Anand

On Wed, 27 Oct 2004 12:09:52 +0200, Stig Hornuff
<sti...@cy...> wrote:
> bit...@gm... wrote:
> 
> >Hello everybody,
> >
> >I'm new to cvs and got a few questions for a project in my company.
> >I'm looking for a way to manage access a CVS repsitory with differnt user
> >permissions to the files and directories on linux. Searching in google
> >haven't brougt good ideas to me.
> >CVS uses in fact, to manage access the file permissions of the file system and
> >optionally, the permissions in writers and readers if you have set them.
> >The bad thing is, that I cannot do some finetuning on the system.
> >When I have 5 Projects, for example with 5 different groups I cannot give an
> >user which belongs to project1 group write access to the project2 directory
> >which belongs to a other group without the option that the other members of
> >project1 group cannot access project2 dir.
> >First I thought, I can solve this problem with the use of the posix acls in
> >ext3. But in my tests a cvs commit with pserver of a modified file changes
> >the the owner and group of the file to the user id and group I do the commit.
> >The attributes which I set before with setfacl are lost then after commit.
> >And finally I haven't find a way that CVS keep the file permissions and
> >uid.gid  on commit as they are in the repository. :-(
> >
> Using pserver connects, you can control which user the cvs server runs
> as using the 3rd column in the passwd file local to cvs (in CVSROOT
> directory).
> Utilizing that enables you to get what you want by setting the 's' bit
> on owner+group on directories and defining runas-users correctly in
> UNIX. Or eventually by using posix acl's.
> In other words: If you can make the setup via normal UNIX users, you can
> do also in cvs - but it can be rather complicated....
> 
> >So I think the use of CVSACL would be the best way to manage the
> >Repository.  ;-)
> >
> Yes! It is far easier and you avoid double administration (just cvs
> instead of UNIX and cvs).
> 
> >But why is CVSACL only a patch and is not included in main cvs?
> >Is it in time more testing, or can it be use in a productive enviroment?
> >For examle on a cvs server in company without the risk of loosing data or
> >server crashing.
> >
> cvs with or witout cvsacl is NOT a safeguard against dataloss and/or
> corruption. Backups are!
> Having said that, then I have yet to see cvs corrupting or losing data
> by itself - and I have used cvs for several years.
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> cvsacl-users mailing list
> cvs...@li...
> https://lists.sourceforge.net/lists/listinfo/cvsacl-users
>

bit...@gm... wrote:

>Hello everybody,
>
>I'm new to cvs and got a few questions for a project in my company.
>I'm looking for a way to manage access a CVS repsitory with differnt user 
>permissions to the files and directories on linux. Searching in google 
>haven't brougt good ideas to me.
>CVS uses in fact, to manage access the file permissions of the file system and 
>optionally, the permissions in writers and readers if you have set them. 
>The bad thing is, that I cannot do some finetuning on the system.
>When I have 5 Projects, for example with 5 different groups I cannot give an 
>user which belongs to project1 group write access to the project2 directory 
>which belongs to a other group without the option that the other members of 
>project1 group cannot access project2 dir.
>First I thought, I can solve this problem with the use of the posix acls in 
>ext3. But in my tests a cvs commit with pserver of a modified file changes 
>the the owner and group of the file to the user id and group I do the commit.
>The attributes which I set before with setfacl are lost then after commit. 
>And finally I haven't find a way that CVS keep the file permissions and 
>uid.gid  on commit as they are in the repository. :-(
>
Using pserver connects, you can control which user the cvs server runs 
as using the 3rd column in the passwd file local to cvs (in CVSROOT 
directory).
Utilizing that enables you to get what you want by setting the 's' bit 
on owner+group on directories and defining runas-users correctly in 
UNIX. Or eventually by using posix acl's.
In other words: If you can make the setup via normal UNIX users, you can 
do also in cvs - but it can be rather complicated....

>So I think the use of CVSACL would be the best way to manage the 
>Repository.  ;-)
>
Yes! It is far easier and you avoid double administration (just cvs 
instead of UNIX and cvs).

>But why is CVSACL only a patch and is not included in main cvs?
>Is it in time more testing, or can it be use in a productive enviroment? 
>For examle on a cvs server in company without the risk of loosing data or 
>server crashing.
>
cvs with or witout cvsacl is NOT a safeguard against dataloss and/or 
corruption. Backups are!
Having said that, then I have yet to see cvs corrupting or losing data 
by itself - and I have used cvs for several years.

On Tuesday 26 October 2004 03:41, bit...@gm... wrote:
> Is it in time more testing, or can it be use in a productive enviroment=
?

I have been using it for about two months in my company without major=20
problems.

> For examle on a cvs server in company without the risk of loosing data =
or
> server crashing.

cvsacl patch does not modify the structure of cvs files.  It only adds ac=
cess=20
control to the files in the repository.  So there are not risk of data=20
corruption.

C=E9sar

Hello everybody,

I'm new to cvs and got a few questions for a project in my company.
I'm looking for a way to manage access a CVS repsitory with differnt user 
permissions to the files and directories on linux. Searching in google 
haven't brougt good ideas to me.
CVS uses in fact, to manage access the file permissions of the file system and 
optionally, the permissions in writers and readers if you have set them. 
The bad thing is, that I cannot do some finetuning on the system.
When I have 5 Projects, for example with 5 different groups I cannot give an 
user which belongs to project1 group write access to the project2 directory 
which belongs to a other group without the option that the other members of 
project1 group cannot access project2 dir.
First I thought, I can solve this problem with the use of the posix acls in 
ext3. But in my tests a cvs commit with pserver of a modified file changes 
the the owner and group of the file to the user id and group I do the commit.
The attributes which I set before with setfacl are lost then after commit. 
And finally I haven't find a way that CVS keep the file permissions and 
uid.gid  on commit as they are in the repository. :-(

So I think the use of CVSACL would be the best way to manage the 
Repository.  ;-)
But why is CVSACL only a patch and is not included in main cvs?
Is it in time more testing, or can it be use in a productive enviroment? 
For examle on a cvs server in company without the risk of loosing data or 
server crashing.
I know it's Offtopic but are there other ways for a flexible access managment 
for a CVS repository?
I would be glade for any help and answers, cause I don't know what I should do 
else or where I can look for a answer.

Best regards

Frank

I set up cvs-1.11.17 with the matching cvsacl-1.2.1 patch. (I also tried 
the same with this merged onto cvs-1.12.9 with pam enabled)

In both cases, everything works just as if the acl patch did not exist. 
I can also manipulate the lists using the racl command, but my remote 
users are always granted access to check out.

I have checked and rechecked my config.  Any suggestions on how to debug?

-Joel Peshkin

Hi,

First of all, CVSServerRunAsUser keyword does not work
when connection type is ssh. It only works with pserver connections.
When CVSServerRunAsUser is set, and connection type is pserver,
file system permissions should allow modify by defined user.

Write or create permissions includes read permissions.
write but not read permission is not possible.

Regards,
sb...@us...

----- Original Message ----- 
From: "Willard Korfhage" <cvs...@fa...>
To: <cvs...@li...>
Sent: Friday, October 22, 2004 5:37 PM
Subject: [cvsacl-users] Allowing writing but not reading.

>I need to set up a repository where one login can put files into the 
>repository, but can't check them out again. I thought that I configured 
>everything correctly, but the ACL's don't prevent checking out files, so I 
>was wondering if I could get some help on what I have done wrong.
>
> The aclconfig file is set up with
>
>    UseCVSACL=yes
>    CVSACLDefaultPermissions=wc
>    CVSServerRunAsUser=cvsca
>
> where cvsca is the administrative account for the repository.
>
> I checked that the access file has a line
>
>    d:ALL:ALL:configwriter!wc:
>
> where configwriter is supposed to be able to write but not read. This 
> repository has a "Practice" module, created by configwriter, that I am 
> using for testing. The permissions on it are:
>
>    $ cvs -d /data/local/cvsca racl -l -d Practice
>    d Practice | HEAD | | defaults ALL: wc
>
> As far as I can tell, everything seems fine. However, if I login to a 
> linux machine as configwriter and do
>
>    cvs -d :ext:configwriter@mumble:/data/local/cvsca co Practice
>
> where CVS_RSH = ssh, then cvs happily gives me the contents of Practice.
>
> Do the file permissions have anything to do with it? I wouldn't think so.
>
> I am using cvsacl 1.2.1 and cvs 1.11.17.
>
> Thanks for any help.
>
> Willard
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out 
> more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> cvsacl-users mailing list
> cvs...@li...
> https://lists.sourceforge.net/lists/listinfo/cvsacl-users
> 

I need to set up a repository where one login can put files into the 
repository, but can't check them out again. I thought that I configured 
everything correctly, but the ACL's don't prevent checking out files, so 
I was wondering if I could get some help on what I have done wrong.

The aclconfig file is set up with

    UseCVSACL=yes
    CVSACLDefaultPermissions=wc
    CVSServerRunAsUser=cvsca

where cvsca is the administrative account for the repository.

I checked that the access file has a line

    d:ALL:ALL:configwriter!wc:

where configwriter is supposed to be able to write but not read. This 
repository has a "Practice" module, created by configwriter, that I am 
using for testing. The permissions on it are:

    $ cvs -d /data/local/cvsca racl -l -d Practice
    d Practice | HEAD | | defaults ALL: wc

As far as I can tell, everything seems fine. However, if I login to a 
linux machine as configwriter and do

    cvs -d :ext:configwriter@mumble:/data/local/cvsca co Practice

where CVS_RSH = ssh, then cvs happily gives me the contents of Practice.

Do the file permissions have anything to do with it? I wouldn't think so.

I am using cvsacl 1.2.1 and cvs 1.11.17.

Thanks for any help.

Willard

   I patched our CVS with the patch just 4 days back and tried it out
(was a bit skeptical if this thing actually worked or was just another
half heartedly written scripting thing).
    I have been managing access control the hard way for some time
now. Also I just migrated a team form VSS to CVS and had my worst
nightmare come true of users removing files and tags !.
   I guess my face already shows a sense of relief after installing
cvs acl.
Thank you,
Dev Anand

On Tuesday 12 October 2004 05:53, Rob Larsen wrote:
> Users cannot create new directorys in existing modules
>
> The acl is set as follows
>
> cvs racl users:rwtc -R -d code
>
>  users is a standard unix group
>

Do you have UseSystemGroups=3Dyes in your aclconfig?
Does your cvs user belong to the users group?

>
>
> Why cant users add directories ?
>

What is exactly the error message you're receiving?

Cesar

Version 

Concurrent Versions System (CVS) 1.11.17 (client/server)
with CVSACL Patch 1.2.1 (cvsacl.sourceforge.net)

Users cannot create new directorys in existing modules 

Permissions are set as follows as in the docs 

 chown -R cvsadmin:cvsadmin CVSROOT
 chmod 2770 cvsadmin:cvsadmin code

 cvsadmin has acl set to p (admin) 

The acl is set as follows 

cvs racl users:rwtc -R -d code

 users is a standard unix group

drwxrws---    3 cvsadmin cvsadmin     4096 Oct 12 12:31 CVSROOT
drwxrws---    3 cvsadmin cvsadmin     4096 Oct 12 12:31 code

Why cant users add directories ?

Help please 

Rob. 

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

Hi All

First of all thanks to the developers of the CVSACL patch for CVS. It's a
very nice feature to have in a system like CVS.

I am facing a problem after applying this patch. I am using MacCVS Pro
3.0a3(Carbon) for accessing the repository from Mac.

I was using a Mac OS X 10.3 server before for my CVS requirements. Before
applying the patch I used cvs v1.10 that comes bundled by default with the
OS. I had a couple of system users who are also the CVS repository users on
that server machine. All the users used the MacCVS Pro for connecting to the
repository using SSH in the Settings panel of the client application. Each
user used their corresponding system user account information for accessing
the repository. There was no 'passwd' file in the CVSROOT folder before.
Everything worked fine except for the access control.

Then we setup another Mac OS X server and applied the patch to check it out.
I created a set of system users and granted them CVS access. Everything
works fine from the WinCVS client now but not from MacCVS Pro. When I use
the same settings as before (with the previous server) I get an error "The
checkout could not be completed because an error -116 occurred." when I try
to checkout the module.

Any ideas why this happens? Apologies if this is a newbie question, but any
help is greatly appreciated.

Thanks
Pradeep

Hello - 
We recently upgraded to version 1.2.1 of the acl along with version 1.11.17
of CVS.  We had previously been using version 1.1.0 of the acl with cvs
1.11.5 successfully.  Now when I try to add a new user to an existing
repository, I get the error 

cvs [racl aborted]: You do not have admin rights on '.'

I am using the same script and command to setup the user as we used with
success previously, the syntax is

cvs -d /cvs/repos racl userid:wtc -r ALL -d ALL

I've looked at the existing access list and my admin user account is still
there with p level permissions.  Is there something we may have missed in
the upgrade or does anyone have any ideas what the issue might be?

Thanks
MaryBeth

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

Hello:

Has anybody been able to successfully compile CVSACL for Windows?

I had a fair number of errors trying to compile CVSACL with source from =
cvs-1.11.17-cvsacl-1.2.1-patched.
I seem to have overcome most of them, but now I have the following:
main.obj : error LNK2001: unresolved external symbol _cvsacl
parseinfo.obj : error LNK2001: unresolved external symbol =
_cvs_server_run_as
parseinfo.obj : error LNK2001: unresolved external symbol =
_cvs_groups_file_locat
ion
parseinfo.obj : error LNK2001: unresolved external symbol =
_cvs_acl_file_location

parseinfo.obj : error LNK2001: unresolved external symbol =
_use_system_groups
parseinfo.obj : error LNK2001: unresolved external symbol =
_use_cvs_groups
parseinfo.obj : error LNK2001: unresolved external symbol =
_given_perms_valid
parseinfo.obj : error LNK2001: unresolved external symbol =
_cvs_acl_default_permi
ssions
parseinfo.obj : error LNK2001: unresolved external symbol =
_stop_at_first_permiss
ion_denied
parseinfo.obj : error LNK2001: unresolved external symbol =
_use_separate_acl_file
_for_each_dir
parseinfo.obj : error LNK2001: unresolved external symbol _use_cvs_acl
.\WinRel\cvs.exe : fatal error LNK1120: 11 unresolved externals
NMAKE : fatal error U1077: 'link.exe' : return code '0x460'

Thanks
Amarjit
Hi Stig,

Thank you,

Regards,
sb...@us...

----- Original Message ----- 
From: "Stig Hornuff" <sti...@cy...>
To: <cvs...@li...>
Sent: Tuesday, July 13, 2004 2:57 PM
Subject: [cvsacl-users] Segmentation fault when using
UseSeperateACLFileForEachDir=yes

> Hi,
>
> For the sake of making cvs-1.11.17-cvsacl-1.2.1-patched work I created a
> small patch for this little problem.
> This thing is that 'accessfilecount' was not initialize if 'file' was
> not null.
>
> By move the accessfilecount up above the if construct (and thus out of
> it), it is insured, that it is initialized to whatever 'intcount' is set
to.
>
> I fooled around with it and made a LOT of directories and files - no
> problems and access rights are handle properly.
>
> Patch is attached!
>
> (If the attachment doesn't come through, then let me know where to put it)
>
> Cheers
> Stig :))
>
>

Hi,

For the sake of making cvs-1.11.17-cvsacl-1.2.1-patched work I created a 
small patch for this little problem.
This thing is that 'accessfilecount' was not initialize if 'file' was 
not null.

By move the accessfilecount up above the if construct (and thus out of 
it), it is insured, that it is initialized to whatever 'intcount' is set to.

I fooled around with it and made a LOT of directories and files - no 
problems and access rights are handle properly.

Patch is attached!

(If the attachment doesn't come through, then let me know where to put it)

Cheers
Stig :))

I set up the repository as outlined in README.CVSACL
under user cvsadm and group cvsadm.  I gave myself administrator priviliages 
and set it up for remote access only.
# Set CVSServerRunAsUser to a system user, in order CVS server
# to run as.
CVSServerRunAsUser=cvsadm 

If I do a remote checkout as myself it works fine, but when I try as another 
user I get : 

cvs server: cannot open /data/.cvsroot/CVSROOT/config: Permission denied
cvs server: cannot open /data/.cvsroot/CVSROOT/aclconfig: Permission denied
Cannot access /data/.cvsroot/CVSROOT 

which tells me it doesn't seem to run as user - right?  Any idea of where I 
went wrong? 

 - Jim

fixed reported errors (thanks Alex, Mark, Liam) in the patch
and uploaded to cvsacl.sourceforge.net as cvsacl-1.2.1 release.
Regards,
sb...@us...
http://cvsacl.sourceforge.net

Thanks for the update.  Everything is compiling okay and cvsacl appears to
be working now with the UseSeparateACLFileForEachDir=yes option.

Alex

On Thu, 24 Jun 2004 sb...@us... wrote:

> Hi,
> 
> Patch works now, when UseSeparateACLFileForEachDir=yes
> UseSeparateACLFileForEachDir is correct spelling, so i changed it.
> Thank you for reporting errors.
> Regards,
> Baris
> sb...@us...
> 

2003	Jan	Feb	Mar	Apr (1)	May	Jun	Jul	Aug (3)	Sep	Oct	Nov	Dec (5)
2004	Jan	Feb (3)	Mar (1)	Apr (2)	May	Jun (20)	Jul (4)	Aug (1)	Sep	Oct (12)	Nov (6)	Dec (4)
2005	Jan	Feb (8)	Mar (9)	Apr (3)	May	Jun	Jul (1)	Aug	Sep	Oct	Nov	Dec
2006	Jan (1)	Feb	Mar (1)	Apr (1)	May (2)	Jun (2)	Jul	Aug	Sep	Oct	Nov (1)	Dec (4)
2007	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug (3)	Sep	Oct (1)	Nov	Dec (1)
2008	Jan	Feb	Mar	Apr	May	Jun (1)	Jul	Aug	Sep	Oct	Nov	Dec
2009	Jan	Feb	Mar (1)	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2010	Jan	Feb	Mar	Apr (3)	May (1)	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2012	Jan	Feb (2)	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

cvsacl-users Mailing List for CVS Access Control List Extension (Page 3)

cvsacl-users — General Discussion List for CVSACL