I have released new :nserver: patch.  From now on, compatibility is
king.   This patch contains support for old pserver clients.  

URL: http://alexm.here.ru/cvs-nserver/cvs-nserver-27-02-2000.diff

This patch is not for general public, e.g. older clients would be able
only to cvs login successfully.  This is for discussion, contemplation
and code auditing.  Though there are not many features left to be able
to fully use both old and new clients (not writing them all now is the
way masochism manifests itself in me...).


>From NEWS file:

+ There is a new access method called :nserver:.  It is cleaner
analogue of :pserver:.  There is also more orthogonal scheme for
authentication using the checkpassword interface
(http://cr.yp.to/checkpassword.html).

It seems like there are three most useful schemes for setting up you
CVS-server:

a) :nserver: protocol, virtual users:

cvs-nserver /repos1 ... /reposN -- cvs.example.org cvschkpw cvs nserver

Advantages: remote administration of repositories (cvs passwd
command);  new extensible protocol.

b) :pserver: protocol, virtual users:

cvs-pserver /repos1 ... /reposN -- cvschkpw cvs pserver

Advantages: remote administration of repositories; complete
compatibility with older clients.

c) :pserver: protocol, system users:

cvs-pserver /repos1 ... /reposN -- checkpassword cvs pserver

Advantages: simpler and cleaner code (compare ~6000 lines of server.c
against <200 of cvs-pserver.c);  checkpassword-compatible
authentificator can use e.g. PAM or any other system-level
authentication mechanism. 

When using cvschkpw, authentication is done against CVSROOT/cvspasswd
file containing much more information about CVS users than
CVSROOT/passwd + CVSROOT/users.  This file could also be managed with
``cvs passwd'' command, locally or over the network.

It seems to be a very little sense in running :nserver: protocol with
system users.


Hope that helps.  If somebody has missed the announce of cvs-nserver
mailing list then here it is.  I would especially be glad to see here
Win32 people as I am not competent in Windows NT security (yet):

+ There is a [EMAIL PROTECTED] mailing list.  

You can subscribe by sending any message to
[EMAIL PROTECTED]  

You can unsubscribe by sending any message to
[EMAIL PROTECTED]

The list is managed by ezmlm and it will tell you about its useful
functionality in welcome-messages.

Please note that this list is run on my home machine and on my home
dialup so please take care of netiquette and also expect non-momentary 
distribution.

WATCH AND PREY!

--

Let no shadow fall over thee            // tragedy me

Reply via email to