SSH Reference Manual

ALLOW-PTY must be set to YES for this attribute to be accepted for 6530 SSH clients, such as MR-Win6530 or J6530.
If *MENU* is followed by a service or window name, the corresponding service or window is automatically selected. If
the service or window does not exist, the STN menu will be displayed.
If the option FORCE is appended, then the user is forced to use the pre-configured STN service or window. In this case
the user will not see the STN menu, even when the configured service or window does not exist.
COMMENT
Enables administrators to input free text that describes an entity or provides a short explanation of the intended use of the
USER entity or, when COMMENT is used for a PUBLICKEY, for the user public key. The entire comment must be
enclosed in double quotes if the comment includes spaces. The content will not be used for any processing.
CPU-SET
Defines a set of CPUs used when processes (except SFTPSERV processes) are invoked directly by SSH2 (for
SFTPSERV processes the attribute SFTP-CPU-SET is used instead). CPUs are assigned via a round-robin algorithm
among all the configured CPUs that are available.
The value can be a CPU number (e.g. 2), a range of CPUs (e.g. 3-4), or a comma-separated list of CPU numbers and
CPU ranges, enclosed in parentheses, e.g. (2, 5-7, 9).
The default is to start user processes in the same CPU in which the SSH2 process is running. In this case, the processing
load is spread by using multiple SSH2 processes and starting these SSH2 processes in different CPUs).
If no value is specified, the value will be reset to the default. The default is to use the value of SSH2 parameter CPUSET
to determine a CPU or, if that is not set, the CPU the SSH2 process is running in is used.
DELETE PRINCIPAL
Deletes the principal name specified by <user>@<REALM>, a pattern or all principal names from the list of principal
names defined for the user. If more than one valid principal name is to be deleted by name, then there must be one
DELETE PRINCIPAL <user>@<REALM> attribute for each principal name. If *@<REALM> is specified the entry
*@<REALM> is removed and not all principal names ending in <REALM>. Similarly, when *@* is specified the
principal entry *@* is removed from the list of principals. If all entries need to be removed from the user's list of
principals the wildcard * can be used, i.e. DELETE PRINCIPAL *.
DELETE PUBLICKEY
This attribute deletes the public key identified by <key-name> or all public keys of the user when wildcard * is specified.
EXPIRE-DATE
This optional attribute of an ssh user’s PUBLICKEY entry is used to set the EXPIRE-DATE (not-valid-after date) for the
public key. This attribute can only be set if the life-cycle policy for User Public Keys is enabled (determined by SSH2
parameter LIFECYCLEPOLICYPUBLICUSERKEY). If SSH2 parameter LIFECYCLEPOLICYPUBLICUSERKEY is
set to FIXED, then field EXPIRE-DATE can be modified by the SUPER.SUPER user only (unless explicitly denied in
OBJECTTYPE USER record) or those configured with full SSHCOM access. In case the SSH2 parameter
LIFECYCLEPOLICYPUBLICUSERKEY is set to VARIABLE, then every user with partial SSHCOM access can
change field EXPIRE-DATE.
LIVE-DATE
This optional attribute of an ssh user’s PUBLICKEY entry is used to set the LIVE-DATE (not-valid-before date) for the
public key. This attribute can only be set if the life-cycle policy for User Public Keys is enabled (determined by SSH2
parameter LIFECYCLEPOLICYPUBLICUSERKEY). If SSH2 parameter LIFECYCLEPOLICYPUBLICUSERKEY is
set to FIXED, then field LIVE-DATE can be modified by the SUPER.SUPER user only (unless explicitly denied in
OBJECTTYPE USER record) or those configured with full SSHCOM access. In case the SSH2 parameter
LIFECYCLEPOLICYPUBLICUSERKEY is set to VARIABLE, then every user with partial SSHCOM access can
change field LIVE-DATE.
OWNER
178 • SSHCOM Command Reference HP NonStop SSH Reference Manual