[Top] [Prev] [Next] [Contents] [Index]

Setting Up Host-Based Access Control for Configuration Data

This section describes how to control which hosts have remote interactive access to a terminal's Configuration and Preferences daemons. Excluding a host from this form of access does not mean that the host cannot download remote configuration files to the terminal; it only prevents remote access through a TELNET connection or Change Setup Parameters, Change Quick Setup, and Change User Preferences.

Host access control is turned off by default, allowing access to configuration data from any host. You can allow access from a list of specified hosts or prevent all access.

Allowing Access from Specified Hosts

To establish a list of hosts that have access to a terminal's configuration data:

You can now access the terminal's Configuration and User Preferences daemons remotely only from a host listed in the config-access-control-list table.

Preventing All Remote Access to the Terminal's Configuration Data

If no hosts should have access to the terminal's configuration data, set the config-access-control-enabled parameter to "true" and make sure the config-access-control-list table is empty, that is:


config-access-control-list = {}

The terminal's Configuration and User Preferences daemons can now be accessed only locally through Change Setup Parameters, Change Quick Setup, and Change User Preferences.



[Top] [Prev] [Next] [Contents] [Index]

Send comments, suggestions, or questions about this document to the NCD Technical Publications Department by Internet e-mail. Write to us at techpubs@ncd.com.
Copyright © 1997, NCD Inc. All rights reserved.