Connections not using the CS dialer: clients

Optional or conditional steps

1. Include an invoke-scheme pair in the appropriate Systems(4bnu) or Dialers(4bnu) file entry. For example:

   #Systems file
   #
   sysa Any DK speed sysa INVOKE "cr1 -r"
   sysb Any DKcr1 speed sysb
   

   #Devices file
   #
   DK term/11 - Any datakit \D
   DKcr1 term/11 - Any datakitcr1 \D
   

   #Dialers file
   #
   datakit ""	"" \d TION:--TION: \D
   datakitcr1 ""	"" \d TION:--TION: \D INVOKE "cr1 -r"
   

   Whether calling sysa or sysb, a Datakit^® VCS connection will be made and the cr1 authentication scheme will be invoked in the responder role. See Dialers(4bnu) and Systems(4bnu) for field definitions.

2. Specify authentication for uuxqt. If you want to allow the use of the new features of the uux facility, you must perform this step. For the current release, cr1 key management is the only key management scheme available to BNU for use in authenticating remote execution requests.

   BNU uses the KEYS= and AUTH= values in the Config file or Permissions file. If uuxqt can obtain and successfully decode the authentication information supplied with a request, the request is executed as the mapped user. (See ``Administering ID mapping''.) If no authentication information is supplied and the value of AUTH is opt or no, uuxqt will execute the request as it did in previous releases. If either the decoding of authentication information fails or no authentication was attempted, and the value of AUTH is req or yes, the request will be rejected.

3. Perform cr1 key administration. If you are using the cr1 authentication scheme, you must perform cr1 key administration. See ``cr1 Bilateral Authentication Scheme''.