Go to the first, previous, next, last section, table of contents.

### Direct connection with kerberos

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.

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 request encryption.

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 `CVS_CLIENT_PORT` environment variable 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:chainsaw.brickyard.com:/user/local/cvsroot checkout foo

Previous versions of CVS would fall back to a connection via rsh; this version will not do so.

Go to the first, previous, next, last section, table of contents.