Connection server components

The connection server is made up of the following components:

• An application interface to the standing server. The interface consists of library routines that make the connection over connection-oriented networks or using dialup connections and an error reporting routine. The use of the application interface routines is described in ``The connection server'' and on cs_connect(3N) and dials(3N).

• An /etc/iaf/serve.allow file, maintained on the client machine. /etc/iaf/serve.allow contains a list of network services that client applications expect to use and the acceptable authentication scheme or schemes for each service. This file is not needed if client applications do not authenticate server identities, that is, if client applications will accept any authentication scheme imposed by server machines. /etc/iaf/serve.allow is described in the section ``Maintaining the /etc/iaf/serve.allow file''.

• An optional file, /etc/iaf/serve.alias, also maintained on the client machine. /etc/iaf/serve.alias contains a list of server names, network service names, and their aliases. The file is described in ``Maintaining the /etc/iaf/serve.alias file''.

• A non-standing network service, reportscheme, that tells client machine applications what authentication scheme to use for a requested network service. The reportscheme service must exist on each port monitor that offers network services if the server is to enforce authentication scheme invocation. reportscheme is described in ``The reportscheme service'', in ``The connection server'', and on reportscheme(1Mbnu).

• A connection server log file.

The application interface to the connection server consists of the library routines cs_connect(3N), dials(3N) and cs_perror(3N).