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-4
Altering a Terminal Definition
the priority at which the command interpreter is to execute. For more information about
these parameters, see the Safeguard Reference Manual.
For example, this command adds terminal $TFOX.#T015 and causes TACL to be
started after user authentication at the terminal:
=ADD TERMINAL $tfox.#t015, PROG $system.system.tacl
Use the INFO TERMINAL command to verify the results:
=INFO TERMINAL $tfox.#t015
The display shows:
The display shows that TACL is the command interpreter defined for this terminal. The
terminal is frozen because the terminal definition was just added to the Safeguard
database. To thaw the terminal:
THAW TERMINAL $tfox.#t015
Altering a Terminal Definition
Like other Safeguard protection records, an existing terminal definition record can be
altered.
For example, suppose you want to change the definition for terminal $TFOX.#T015 to
tailor the execution parameters for TACL. This command specifies that TACL is to
execute with a priority of 150 in CPU 4 and that $DATA2 is to be used as the swap
volume. The command also includes parameter text of 5, which TACL interprets as the
backup CPU number.
=ALTER TERMINAL $tfox.#t015, PRI 150, CPU 4, &
=SWAP $data2, PARAM-TEXT 5
Use the INFO TERMINAL command to verify the results:
=INFO TERMINAL $tfox.#t015
TERMINAL $TFOX.#T015 STATUS FROZEN
PROG = $SYSTEM.SYSTEM.TACL
LIB = * NONE *
PNAME = * NONE *
SWAP = * NONE *
CPU = * NONE *
PRI = * NONE *
PARAM-TEXT =