|Version Management with CVS - the CVS manual|
by Per Cederqvist et al.
Paperback (6"x9"), 216 pages, 8 figures
RRP £19.95 ($29.95)
17.3 Direct connection with Kerberos
The easiest way to use Kerberos is to use the Kerberos
rsh, as described in section 2.4.1 Connecting with rsh and ssh.
The main disadvantage of using rsh is that all the data
needs to pass through additional programs, so it may be
slower. So if you have Kerberos installed you can
connect via a direct TCP connection,
authenticating with Kerberos.
This section concerns the Kerberos network security system, version 4. Kerberos version 5 is supported via the GSSAPI generic network security interface, as described in the previous section.
To do this, CVS needs to be compiled with Kerberos support; when configuring CVS it tries to detect whether Kerberos is present or you can use the ‘--with-krb4’ flag to configure.
The data transmitted is not encrypted by
default. Encryption support must be compiled into both
the client and server; use the
‘--enable-encryption’ configure option to turn it
on. You must then use the
-x global option to
You need to edit ‘inetd.conf’ on the server
machine to run
cvs kserver. The client uses
port 1999 by default; if you want to use another port
specify it in the
CVSROOT (see section 2.4 Remote repositories)
CVS_CLIENT_PORT environment variable
(see section C All environment variables which affect CVS) on the client.
When you want to use CVS, get a ticket in the
usual way (generally
kinit); it must be a ticket
which allows you to log into the server machine. Then
you are ready to go:
$ cvs -d :kserver:faun:/usr/local/cvsroot checkout foo
Previous versions of CVS would fall back to a connection via rsh; this version will not do so.
|ISBN 0954161718||Version Management with CVS - the CVS manual||See the print edition|