Safeguard Administrator's Manual (G06.24+, H06.03+)
Table Of Contents
- What’s New in This Manual
- About This Manual
- 1 Introduction
- 2 Controlling User Access
- Introduction
- Using SAFECOM to Establish a Local User Community
- Using SAFECOM to Manage User Access to Your System
- Changing the Owner of a User Authentication Record
- Granting a User Temporary Access to Your System
- Requiring Users to Change Their Passwords
- Granting a Grace Period for Changing an Expired Password
- Forcing Immediate Expiration of a User’s Password
- Freezing a User's Ability to Access the System
- Specifying Auditing for a User ID
- Deleting Users
- Deleting Administrative Groups
- Using SAFECOM to Establish a Network of Users
- Using Safeguard With Nodes With Standard Security
- Identifying Network Users
- Granting a Network User Access to Objects on Your System
- Establishing a Community of Network Users
- Changes to the PAID During a User’s Session
- Additional Considerations for Aliases and Groups
- Additional Considerations for ACCESS with Network Specific Subject IDs
- Establishing Default Protection for a User's Disk Files
- Specifying a Default Command Interpreter for a User
- Establishing Guardian Defaults
- Assigning an Alias to a User
- 3 Managing User Groups
- 4 Securing Volumes and Devices
- 5 OBJECTTYPE Control
- 6 Managing Security Groups
- 7 Securing Terminals
- 8 Warning Mode
- 9 Configuration
- Safeguard Attributes
- Configuring User Authentication
- Configuring Password Control
- Configuring Device Control
- Configuring Process Control
- Configuring Disk-File Control
- Configuring Safeguard Auditing
- Configuring a Default Command Interpreter
- Configuring Communication With $CMON
- Configuring Logon Dialog
- Configuring Exclusive Access at Safeguard Terminals
- Configuring Warning Mode
- Configuring Persistence
- Configuring Attributes for Node Specific Subjects in ACLs
- 10 Installation and Management
- Safeguard Components
- Process Considerations for the SMP and SAFECOM
- Safeguard Subsystem Management Commands
- General Installation Procedure
- Installing the Safeguard Software
- Starting the SMP
- Converting to the Safeguard Subsystem
- Updating the Safeguard Software
- Guidelines for Securing the Safeguard Subsystem
- Monitoring the Safeguard Subsystem
- A SAFECOM Command Syntax
- Index
Securing Terminals
Safeguard Administrator’s Manual—523317-013
7-3
Adding a Terminal Definition
change the configuration record, the command interpreter defined in that record is
$SYSTEM.SYSTEM.TACL.
The Safeguard software can honor the command interpreter specification only at a
terminal that it controls. If the Safeguard software does not control the logon dialog at a
terminal, all command interpreter specifications are ignored at that terminal.
Adding a Terminal Definition
Before you add a terminal definition to the Safeguard database, be sure to stop any
process running at that terminal. If you do not stop the other process, the Safeguard
software competes with it for control of the terminal.
In the most basic form, you can use the ADD TERMINAL command without any
additional parameters to add a terminal definition. Simply specify the name of the
terminal to be added. As is true when you add most other object names, you cannot
use wild-card characters when you specify a terminal name in an ADD command.
This command adds a terminal definition for the terminal $TFOX.#T014:
=ADD TERMINAL $tfox.#t014
This form of the command uses default values for the command interpreter to be
started at the terminal after a user is authenticated.
To thaw terminal $TFOX.#T014, issue this command:
=THAW TERMINAL $tfox.#t014
To verify the results of the commands, use this INFO TERMINAL command:
=INFO TERMINAL $tfox.#t014
The display shows:
The display shows that the terminal is thawed and no command interpreter has been
defined for the terminal.
You can specify a particular command interpreter to be started automatically after user
authentication. To do so, you must specify the name of the object file of the command
interpreter to be invoked. You can also specify several optional parameters, such as
Note. When you add a terminal definition record to the Safeguard database, that terminal
becomes frozen. You must use the THAW TERMINAL command to enable the terminal.
TERMINAL $TFOX.#T014 STATUS THAWED
PROG = * NONE *
LIB = * NONE *
PNAME = * NONE *
SWAP = * NONE *
CPU = * NONE *
PRI = * NONE *
PARAM-TEXT =