[cvsnt] How to get rid of protocols

Gerhard Fiedler lists at connectionbrazil.com
Thu Apr 20 16:41:43 BST 2006


Hello,

I'd like to have only the sspi protocol available to clients for access to
files (and possibly the enum protocol) -- unless there is a reason to
provide other protocols. So my first question is: Is there a reason to have
other protocols available, if the intention is to only allow repository
access through sspi? (May sound a bit silly, but then... you never know :)

For example, there may be a reason to leave the enum "protocol" available.
(I put protocol in quotes, because it is a protocol, but it doesn't seem to
be a normal repository access protocol.)


Then, when looking at my configuration, I didn't quite understand what
actually is available. The following command is supposed to tell me what
protocols are available on my server:

p:\>cvs info -s
Available protocols on server:

enum                enum 2.5.03 (Scorpio) Build 2151
sspi                sspi 2.5.03 (Scorpio) Build 2151

Looks good so far. However, when I look at the list of plugins at the
server, I see also the server and ssh protocols. Differently from the other
protocols listed there (which are all disabled, except sspi and enum), they
don't have a configuration that would allow to en/disable the protocol. Now
I wonder whether they are available or not, and what determines this. Their
DLLs are present, and they are listed in the plugins tab of the control
panel applet. But they are not listed with the info -s command.


Here's what I'm using:

p:\>cvs ver
Client: Concurrent Versions System (CVSNT) 2.5.03 (Scorpio) Build 2151
(client/server)
Server: Concurrent Versions System (CVSNT) 2.5.03 (Scorpio) Build 2151
(client/server)

Thanks for any help or pointers,
Gerhard



More information about the cvsnt mailing list