Rename Key - HP NonStop SSH 544701-014 Reference Manual

CREATION-DATE
This attribute contains the creation date of a key and is automatically set when a key is generated or imported. If a key
was generated or imported before the introduction of the CREATION-DATE attribute, the value will be shown as
*NONE*, meaning 'not set'.
LIVE-DATE
This optional attribute contains the date the key has gone or will go into state 'LIFE'. The key is not valid before that
date and will not be used for authentication. If a key was generated or imported before the introduction of the LIVE-
DATE attribute, or if an attribute value was not specified in a GENERATE KEY or IMPORT KEY command, then the
value will be shown as *NONE*, meaning 'not set'. The field can be modified using the ALTER KEY command,
depending on the value of SSH2 parameter LIFECYCLEPOLICYPRIVATEUSERKEY.
EXPIRE-DATE
This optional attribute contains the date the key has gone or will go into state 'LIFE'. The key is not valid after that date
and will no longer be used for authentication if the expiration date is reached. If a key was generated or imported before
the introduction of the EXPIRE-DATE attribute, or if an attribute value was not specified in a GENERATE KEY or
IMPORT KEY command, then the value will be shown as *NONE*, meaning 'not set'. The field can be modified using
the ALTER KEY command, depending on the value set of SSH2 parameter LIFECYCLEPOLICYPRIVATEUSERKEY.
LIFE-CYCLE-STATE
The value of field LIFE-CYCLE-STATE (the shortcut LIFE-CYCLE is used in the brief output of the INFO KEY
command) is not actually held in the KEY database record but is determined from CREATION-DATE, LIVE-DATE and
EXPIRE-DATE. The state 'LIFE' is assumed for keys generated or imported before the introduction of the user private
key life-cycle.
LAST-USE
The timestamp of the last usage of the key.
LAST-MODIFIED
The timestamp of the last modification of the key.
STATUS
Whether the key is FROZEN or THAWED.

RENAME KEY

The RENAME KEY command is used to rename a key entry in the SSH database. A key entry can only be renamed by
the SUPER.SUPER user (unless explicitly denied in OBJECTTYPE USER record) or those configured with full
SSHCOM access or by the user who owns the key. The command has the following syntax:
RENAME KEY [<old-system-user-name>:]<old key name>,
[<new-system-user-name>:]<new key name>
The individual attributes have the following meaning and syntax:
<old-system-user-name>
A valid GUARDIAN user who owns the key entry in the user database before renaming it. If <user name> is omitted,
either the user being set with a previously issued ASSUME USER command or the issuer of the RENAME KEY
command will be used as the default. If <user name> is specified, it MUST be followed by a ':' to separate it from the
key name.
<old key name>
Specifies the name of a key entry, which must already exist in the user database, before it is renamed.
SSHCOM Command Reference • 175
HP NonStop SSH Reference Manual