cvsacl-users

[cvsacl-users] Allowing writing but not reading.

[Willard K. <cvs...@fa...>]

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

Re: [cvsacl-users] Allowing writing but not reading.

[sbaris <sb...@us...>]

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
>