[cvsnt] Impact of cvsroot/config SystemAuth- setting when usi ng sspi (and not pserver) to administer CVS

Adrian Crossley adrian.crossley at hesa.ac.uk
Wed Oct 13 09:17:22 BST 2004


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.


>From the manual: "If SystemAuth = Yes the user is considered to be an
administrator ... if they are in the 'Administrators' group (NT) ..."

Also you can set the permissions on CVSROOT to restrict changes to that too
e.g.
xcacls c:\cvsnt /T /P                       BUILTIN\Administrators:F "NT
AUTHORITY\SYSTEM:F" /Y
xcacls c:\cvsnt\cvsroot /T /E /G            HESA_NTNET\cvs-dev:C
xcacls c:\cvsnt\cvsroot\CVSROOT  /T /E /R   HESA_NTNET\cvs-dev

>From what I have read CVSNT was originally a windowsNT port of cvs.  It now
has features that are still sadly lacking in the original cvs and has also
been back-ported to run on *nix systems too.

hope this helps
Ade

-----Original Message-----
From: BERTIN Philippe [mailto:philippe.bertin at cnh.com]
Sent: Wednesday 13 October 2004 09:04
To: 'cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook'
Subject: [cvsnt] Impact of cvsroot/config SystemAuth- setting when using
sspi (and not pserver) to administer CVS


'Llo All,

After some quests for information on how to administer CVS (on CVSNT), it is
still unclear to me how to administer CVS using the sspi- protocol. I tried
on the cvsgui newsgroup, but after a hint from someone, I try my same
question here.
I understand that in cvsroot/config, there is a setting "SystemAuth" that
should be set to no, in order to have cvsroot/admin be taken into account
for determining who can administer CVS. But elsewhere, I see that
cvsroot/admin is only considered when using pserver as the protocol. So I'd
tend to think that I should set SystemAuth to yes. But then I don't know how
to add an adminstrator to CVSNT ...

This altogether makes it still unclear to me how I can administer CVS using
sspi, because that is the protocol I want to use in the long run. I could
eventually make a pserver entry to be able to administer CVS using the
pserver- protocol, but I would like to disable the pserver- protocol
completely (for security purposes, I'd like to delete pserver_protocol.dll).

Another thing (not on the subject line, though) is not 100% clear: the
open-source cvs- daemon that is generally delivered with Linux systems (e.g.
with SuSE), is that CVSNT ? Or what is the relation between these 2 (i.e.
between the open-source cvs daemon and CVSNT) ?

Kind regards,

PhB.
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs

______________________________________________________________

This incoming email was virus scanned for HESA by MessageLabs.
______________________________________________________________


______________________________________________________________

This outgoing email was virus scanned for HESA by MessageLabs.
______________________________________________________________


More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook