[cvsnt] Configuring cvsnt 2.0.58d for access via SSPI

[Bo Berglund]

You can use NTFS file permission settings on the modules to limit access to
users or groups.
If you do so then the directories/files that are set non-accessible to certain
persons will not be possible to access even via cvs.

It is simplest to use groups for this because then you can assign permissions
by adding persons to the groups, for example create the following groups:
CVSReaders	Only read access to the complete repository
CVSWriters	Read/Write access to the repository, no access to CVSROOT
CVSAdmins	Full access to all folders and files in the repository

Now by adding people to these groups you give them permissions on CVS.
Noone not a member of any of these groups will be able to do anything with CVS.

/Bo


-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Bill Powell
Sent: den 11 januari 2005 14:09
To: cvsnt at cvsnt.org
Subject: [cvsnt] Configuring cvsnt 2.0.58d for access via SSPI


I'm a novice setting up cvsnt for the first time on a local network.  I've 
installed cvsnt on a Win2K machine, gone through the installation notes, 
gotten a repository setup, and I'm able to access a Test project using SSPI
(:sspi:cvs_server_machine:/cvsrepo) with no login or password.  My preferred 
client is TortoiseCVS.

I'd like to limit the access to various modules within the repository so 
that ProjectX can be used by only User1, User2, or User3 and not anyone with 
valid priviledges on the domain.

It's not clear to me from the Installation Tips how to limit access to 
various modules using SSPI.

Can anyone shed some light on this for me?

Thanks,
Bill 


_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt