Dell-SSH-MIB Table View

This table contains the router's public key.  Each row in this table
contains a fragment of the key, in printable binhex format.  There may
be up to 160 characters in every fragment, and they are all combined
to form one key.  The key is generated by writing to
rlSshServerRegenerateHostKey.  To cause clients to connect to this router
without printing warning messages (and also prevent active
man-in-the-middle), the router's public key must printed out and inserted
into the client's authorized_keys file

This table contains the fingerprint for the router's public key.

This table contains public keys for all users who are authorized to access
the router.  For a user to be able to log in using SSH, the user name must
appear in this table, and the user's public key must match the one found
here.

This table contains the fingerprints of the public keys for all users who
are authorized to access the router.
To prevent man in the middle attacks, users should make sure the
user's fingerprint, as printed in the connection process, is similar
to the one printed here.

Each row in this table corresponds to an active SSH session with
the server

Each row in this table corresponds to an active SSH session with the server

This table can be used for 2 purposes:
1) Importing public/private key pair to serve as the device key when acting
as SSH server. This is done by setting entries to this table, according to
the specified format. When the last entry (footer) is set, the whole key
pair is checked and if valid, stored in CDB.
2) Exporting the device SSH server public/private key. This can be done by
performing GetNext operations on this table.

This table contains the router's client self public key.  Each row in
this table contains a fragment of the key, in printable binhex format.
There may be up to 160 characters in every fragment, and they are all
combined to form one key.  The key is generated by writing to
rlSshClientRegenerateSelfKey.  To cause clients to connect to this router
without printing warning messages (and also prevent active
man-in-the-middle), the router's public key must printed out and
inserted into the client's authorized_keys file

This table contains the fingerprint for the client's self key.

This table allows the user to change the password in a remote SSH server.
It should be used when working with 'password' authentication with remote
server in SCP sessions.
Set operation on this table will initiate SCP session with the SSH server
whose inet address is specified in the key rlSshClientPasswordChangeInetAddress.
During this session the password for username rlSshClientPasswordChangeUsername
will be changed in the server from rlSshClientPasswordChangeOldPassword to
rlSshClientPasswordChangeNewPassword.
The Set operation might fail, in case an SCP session is already being
held. In case 'noError' is returned, the user can poll the fields
rlSshClientPasswordChangeStatus and rlSshClientPasswordChangeFailureReason
in order to get information on operation status and possible failure
reason. Note: up to 3 status records can be saved.

This table can be used for 2 purposes:
1) Importing public/private key pair to serve as the device key when acting
as SSH client. This is done by setting entries to this table, according to
the specified format. When the last entry (footer) is set, the whole key
pair is checked and if valid, stored in CDB.
2) Exporting the device SSH client public/private key. This can be done by
performing GetNext operations on this table.

Table for storing fingerprints of remote servers public keys. It is used for
the purpose of server authentication. An entry can be inserted to this table
either explicitly by user configuration, or during copy operation, after
user's approval.