CISCOSB-SSH-MIB
AI MIB Summary
The CISCOSB-SSH-MIB module enables monitoring and management of Secure Shell (SSH) service parameters, including active session states, connection counts, and authentication failure events, specifically on Cisco SB (Service Provider) software platforms.
The MIB module describes the private MIB for SSH supported by CISCOSB's software and products.
Main OID:
rlSsh.1.3.6.1.4.1.9.6.1.101.78
97
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
97 total| Object Name |
|---|
rlSshThe MIB module describes the private MIB for SSH supported by CISCOSB's software and products. MODULE-IDENTITY .1.3.6.1.4.1.9.6.1.101.78 |
rlSshMibVersionThe MIB version. The current version is 2ro INTEGER .1.3.6.1.4.1.9.6.1.101.78.1 |
rlSshServer OBJECT IDENTIFIER .1.3.6.1.4.1.9.6.1.101.78.2 |
rlSshServerHostPublicKeyTableThis 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 SEQUENCE OF RlSshServerHostPublicKeyTableEntry .1.3.6.1.4.1.9.6.1.101.78.2.1 |
rlSshServerHostPublicKeyTableEntryThe row definition for this table. RlSshServerHostPublicKeyTableEntry .1.3.6.1.4.1.9.6.1.101.78.2.1.1 |
rlSshServerHostPublicKeyAlgorithmIdentifies the type of public key to be displayed.ro RlSshPublicKeyAlgorithm .1.3.6.1.4.1.9.6.1.101.78.2.1.1.1 |
rlSshServerHostPublicKeyFragmentIdIdentifies the index of this fragment in the final key. All segments must be combined to form one big key.ro Unsigned32 .1.3.6.1.4.1.9.6.1.101.78.2.1.1.2 |
rlSshServerHostPublicKeyFragmentTextA part of the readable text entry for the server's public authorzation key.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.2.1.1.3 |
rlSshServerHostPublicKeyFingerprintTableThis table contains the fingerprint for the router's public key. SEQUENCE OF RlSshServerHostPublicKeyFingerprintTableEntry .1.3.6.1.4.1.9.6.1.101.78.2.2 |
rlSshServerHostPublicKeyFingerprintTableEntryThe row definition for this table. RlSshServerHostPublicKeyFingerprintTableEntry .1.3.6.1.4.1.9.6.1.101.78.2.2.1 |
rlSshServerHostPublicKeyFingerprintAlgorithmIdentifies the type of public key to be displayed.ro RlSshPublicKeyAlgorithm .1.3.6.1.4.1.9.6.1.101.78.2.2.1.1 |
rlSshServerHostPublicKeyFingerprintDigestFormatFormat of the digest to be displayed (OpenSSH or SSH.com).ro RlSshPublicKeyDigestFormat .1.3.6.1.4.1.9.6.1.101.78.2.2.1.2 |
rlSshServerHostPublicKeyFingerprintSECSH format fingerprint of the server's public key. To prevent man in the middle attacks, users should make sure the ssh Server's fingerprint, as printed in the connection process, is similar to the one printed here.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.2.2.1.3 |
rlSshServerAuthorizedUsersPublicKeyTableThis 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. SEQUENCE OF RlSshServerAuthorizedUsersPublicKeyTableEntry .1.3.6.1.4.1.9.6.1.101.78.2.3 |
rlSshServerAuthorizedUsersPublicKeyTableEntryThe row definition for this table. RlSshServerAuthorizedUsersPublicKeyTableEntry .1.3.6.1.4.1.9.6.1.101.78.2.3.1 |
rlSshServerAuthorizedUserNameName of the user who owns this public key. Both the user name and the key bytes must match before a user is authenticated using this key.rw DisplayString .1.3.6.1.4.1.9.6.1.101.78.2.3.1.1 |
rlSshServerAuthorizedUserPublicKeyFragmentIdIdentifies the index of this fragment in the final key. All segments must be combined to form one big key.rw Unsigned32 .1.3.6.1.4.1.9.6.1.101.78.2.3.1.2 |
rlSshServerAuthorizedUserPublicKeyFragmentTextA part of the readable text entry for the user's public authorzation key.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.2.3.1.3 |
rlSshServerAuthorizedUserPublicKeyFragmentStatusCreate or delete a fragment of the user's public key. A user is deleted if it has no remaining fragments.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.2.3.1.4 |
rlSshServerAuthorizedUsersPublicKeyFingerprintTableThis 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. SEQUENCE OF RlSshServerAuthorizedUsersPublicKeyFingerprintTableEntry .1.3.6.1.4.1.9.6.1.101.78.2.5 |
rlSshServerAuthorizedUsersPublicKeyFingerprintTableEntryThe row definition for this table. RlSshServerAuthorizedUsersPublicKeyFingerprintTableEntry .1.3.6.1.4.1.9.6.1.101.78.2.5.1 |
rlSshServerAuthorizedUserFingerprintNameName of the user who owns this public key. Both the user name and the key bytes must match before a user is authenticated using this key.rw DisplayString .1.3.6.1.4.1.9.6.1.101.78.2.5.1.1 |
rlSshServerAuthorizedUserPublicKeyFingerprintAlgorithmIdentifies the type of public key to be displayed.ro RlSshPublicKeyAlgorithm .1.3.6.1.4.1.9.6.1.101.78.2.5.1.2 |
rlSshServerAuthorizedUserPublicKeyFingerprintDigestFormatFormat of the digest to be displayed (OpenSSH or SSH.com).ro RlSshPublicKeyDigestFormat .1.3.6.1.4.1.9.6.1.101.78.2.5.1.3 |
rlSshServerAuthorizedUserPublicKeyFingerprintSECSH format fingerprint of the user's public key. To prevent man in the middle attacks, users should make sure their ssh fingerprint, as printed in the connection process, is similar to the one printed here.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.2.5.1.4 |
rlSshServerSessionTableEach row in this table corresponds to an active SSH session with the server SEQUENCE OF RlSshServerSessionTableEntry .1.3.6.1.4.1.9.6.1.101.78.2.6 |
rlSshServerSessionTableEntryThe row definition for this table. RlSshServerSessionTableEntry .1.3.6.1.4.1.9.6.1.101.78.2.6.1 |
rlSshServerSessionIdentifierIdentifies the connection to which this row corresponds.ro Unsigned32 .1.3.6.1.4.1.9.6.1.101.78.2.6.1.1 |
rlSshServerSessionPeerAddressThe network address of the remote host connected to the server.ro IpAddress .1.3.6.1.4.1.9.6.1.101.78.2.6.1.2 |
rlSshServerSessionPeerPortThe source network port of the remote host connected to the server.ro Unsigned32 .1.3.6.1.4.1.9.6.1.101.78.2.6.1.3 |
rlSshServerSessionPeerVersionThe client version of the remote host connected to the server.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.2.6.1.4 |
rlSshServerSessionUsernameSSH authenticated name of user connected to the server.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.2.6.1.5 |
rlSshServerSessionCipherData encryption cipher used in this connection.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.2.6.1.6 |
rlSshServerSessionHMACMessage authentication code used in this connection.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.2.6.1.7 |
rlSshServerSessionInetTableEach row in this table corresponds to an active SSH session with the server SEQUENCE OF RlSshServerSessionInetTableEntry .1.3.6.1.4.1.9.6.1.101.78.2.7 |
rlSshServerSessionInetTableEntryThe row definition for this table. RlSshServerSessionInetTableEntry .1.3.6.1.4.1.9.6.1.101.78.2.7.1 |
rlSshServerSessionInetIdentifierIdentifies the connection to which this row corresponds.ro Unsigned32 .1.3.6.1.4.1.9.6.1.101.78.2.7.1.1 |
rlSshServerSessionInetPeerAddressTypeThe network address of the remote host connected to the server.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.6.1.101.78.2.7.1.2 |
rlSshServerSessionInetPeerAddressThe network address of the remote host connected to the server.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.6.1.101.78.2.7.1.3 |
rlSshServerSessionInetPeerPortThe source network port of the remote host connected to the server.ro Unsigned32 .1.3.6.1.4.1.9.6.1.101.78.2.7.1.4 |
rlSshServerSessionInetPeerVersionThe client version of the remote host connected to the server.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.2.7.1.5 |
rlSshServerSessionInetUsernameSSH authenticated name of user connected to the server.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.2.7.1.6 |
rlSshServerSessionInetCipherData encryption cipher used in this connection.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.2.7.1.7 |
rlSshServerSessionInetHMACMessage authentication code used in this connection.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.2.7.1.8 |
rlSshServerImportExportSelfKeyTableThis 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. SEQUENCE OF RlSshServerImportExportSelfKeyEntry .1.3.6.1.4.1.9.6.1.101.78.2.8 |
rlSshServerImportExportSelfKeyEntryThe row definition for this table. RlSshServerImportExportSelfKeyEntry .1.3.6.1.4.1.9.6.1.101.78.2.8.1 |
rlSshServerImportExportSelfKeyAlgorithmIdentifies the type of key pair. RlSshPublicKeyAlgorithm .1.3.6.1.4.1.9.6.1.101.78.2.8.1.1 |
rlSshServerImportExportSelfKeyFormatSpecifies the format of public/key pair. The following formats are supported for import/export: 1) uuencoded_format - in this format both private and public key are in uu-encoded format, and are seperated from one another by header and footer. An example of the concateneation of all fragments in this format is: -----BEGIN RSA PRIVATE KEY----- tDaNkZZoCxXfkLLsLDlZ6T9H8U4Gz637eRV7BYBpapkidAxY1UG0/qgfKLPkbId4wzht6ArV9bE4fMtX wSMOxL3q31pOmUdVhjbWYcgZQBDy1DjFSbuIEdP85c96B9bBE2nPv90mSvb/6j8R2NItT/KJeiYMtLtI N3m6/zESKJGIrX0jP1RFDjVZSS5chSAFgB0egsLZEyOQn7jAqpX/x/easD2J6F/OjPXlJ9Hff2tMb3NU QYyBoWH2J9IxhWB6Vo66R9Y04JGR18uL/rV2sMCtpg5ppkVTEpNTp9qE1yXocR2NmzUfNFap+GJ4IHj8 CzkVfmJM/kEWaJsYgHbAgLyRg4QVyelfobv1B71aQ+u1z9KGu/QajkWdR04OQfsGOL1CvU2LGYDcRjfH jv+jl/UkDRRjoD9kt2WvouT+OL6esvKl0OJBqWbGNXg9TWv/VLtJIwgUno+MLaJuOM4Fh44+wpnqUXwQ TFtBFc8pzt5BoOwbv9gXpicTkq4/+GhwXWXxSVFebKhnHAvKSLT+Ba7K7ZeR8EIIxbXdDNFOiS45R2KI jxxXLXK44u6KGl5MygCKXUOFlJ+Zhgrq6ZH17z/RVJQ2CWqb5Ekn9GY3kH9QZ3mb4MDPfriWi2lHGXHY JmJd4SLQhpBdnOS5tu84QmyU3dNbAdzghDsR+dEY/6g7Cn0kcVkeHNZ0H+mCZik5f6XBD8eplkk43bdR FrkwTeAjwurGcKwdiKkR4DlfSq3DKssVBucTqUpqsKqPXLwTIL44rWKhEPXgGPB2XDG0VLvIRKkAgEGI LNTwOm091Ro= -----END RSA PRIVATE KEY----- -----BEGIN RSA PUBLIC KEY----- MIGHAoGBAOeIC9gRg3YaEGGMp3C00qNwLINAEDZV/J4BWM5WnWwCWZyHXDs2XiEmFu0ZONAD4gcT2f2f NNfCBPye39VVuOkKQuSV0MLLX5800LZ4y1BNcPzPZHpnGaCzl7iAjhfj9MolzAh5VRjeiYt0t1um4dm+ q9A4BtfpJqDYxCW9uxd/AgEj -----END RSA PUBLIC KEY----- Enumeration .1.3.6.1.4.1.9.6.1.101.78.2.8.1.2 |
rlSshServerImportExportSelfKeyFragmentIdIdentifies the index of this fragment in the key pair input/output. INTEGER .1.3.6.1.4.1.9.6.1.101.78.2.8.1.3 |
rlSshServerImportExportSelfKeyFragmentTextA part of the readable text entry for the key pair input/output.rw OCTET STRING .1.3.6.1.4.1.9.6.1.101.78.2.8.1.4 |
rlSshServerPortSpecifies the TCP port used by the SSH 2 Server to listen for incoming connections.rw Unsigned32 .1.3.6.1.4.1.9.6.1.101.78.2.101 |
rlSshServerEnableEnables listening for incoming SSH2 connections on the port defined in rlSshServerPort.rw Enumeration .1.3.6.1.4.1.9.6.1.101.78.2.102 |
rlSshServerEnablePublicKeyAuthenticationIf PK authentication is enabled, incoming SSH connections are authenticated using public key authentication (using rlSshServerAuthorizedUsersPublicKeyTable), before authenticating using the router's standard AAA.rw Enumeration .1.3.6.1.4.1.9.6.1.101.78.2.103 |
rlSshServerRegenerateHostKeySetting to a value other than none results in the Server (Host) Key being regenerated. The key size is host-specific.rw RlSshPublicKeyAlgorithm .1.3.6.1.4.1.9.6.1.101.78.2.104 |
rlSshServerDefaultKeyFlagThis scalar indicates which of the SSH server keys are default keys (automatically generated).ro Enumeration .1.3.6.1.4.1.9.6.1.101.78.2.105 |
rlSshServerDeleteSelfKeySetting to a value other than 'none' results in deleting the server self key of the chosen type. As a result a default key may be created (according to the MTSC..)rw RlSshPublicKeyAlgorithm .1.3.6.1.4.1.9.6.1.101.78.2.106 |
rlSshServerEnablePublicKeyAuthAutoLoginIf PK authentication is succesfull and AAA local DB method is enabled for SSH line, the username is checked with AAA local DB. If present, the user is authenticated automatically without prompting for username or password.rw Enumeration .1.3.6.1.4.1.9.6.1.101.78.2.107 |
rlSshServerEnablePasswordAuthenticationIf password authentication is enabled, incoming SSH connections are authenticated with username/password authentication using the router's standard AAA.rw Enumeration .1.3.6.1.4.1.9.6.1.101.78.2.108 |
rlSshClient OBJECT IDENTIFIER .1.3.6.1.4.1.9.6.1.101.78.3 |
rlSshClientUserNameSpecifies the default user name the ssh client will use when authenticating to a remote server. In SCP sessions this global user name will be used unless a specific user name has been specified for the operation. The value of this MIB must not contain charachters ':' or '@' (those are used to indicate parameters seperation in SCP copy).rw DisplayString .1.3.6.1.4.1.9.6.1.101.78.3.1 |
rlSshClientRegenerateSelfKeySetting to a value other than none results in the client self key being regenerated. The key size is host-specific.rw RlSshPublicKeyAlgorithm .1.3.6.1.4.1.9.6.1.101.78.3.2 |
rlSshClientSelfPublicKeyTableThis 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 SEQUENCE OF RlSshClientSelfPublicKeyTableEntry .1.3.6.1.4.1.9.6.1.101.78.3.3 |
rlSshClientSelfPublicKeyTableEntryThe row definition for this table. RlSshClientSelfPublicKeyTableEntry .1.3.6.1.4.1.9.6.1.101.78.3.3.1 |
rlSshClientSelfPublicKeyFragmentIdIdentifies the index of this fragment in the final key. All segments must be combined to form one big key.ro Unsigned32 .1.3.6.1.4.1.9.6.1.101.78.3.3.1.1 |
rlSshClientSelfPublicKeyAlgorithmIdentifies the type of public key to be displayed.ro RlSshPublicKeyAlgorithm .1.3.6.1.4.1.9.6.1.101.78.3.3.1.2 |
rlSshClientSelfPublicKeyFragmentTextA part of the readable text entry for the router's client public authorization key.rw DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.3.3.1.3 |
rlSshClientSelfPublicKeyFingerprintTableThis table contains the fingerprint for the client's self key. SEQUENCE OF RlSshClientSelfPublicKeyFingerprintTableEntry .1.3.6.1.4.1.9.6.1.101.78.3.4 |
rlSshClientSelfPublicKeyFingerprintTableEntryThe row definition for this table. RlSshClientSelfPublicKeyFingerprintTableEntry .1.3.6.1.4.1.9.6.1.101.78.3.4.1 |
rlSshClientSelfPublicKeyFingerprintAlgorithmIdentifies the type of public key to be displayed.ro RlSshPublicKeyAlgorithm .1.3.6.1.4.1.9.6.1.101.78.3.4.1.1 |
rlSshClientSelfPublicKeyFingerprintDigestFormatFormat of the digest to be displayed (OpenSSH or SSH.com).ro RlSshPublicKeyDigestFormat .1.3.6.1.4.1.9.6.1.101.78.3.4.1.2 |
rlSshClientSelfPublicKeyFingerprintSECSH format fingerprint of the client's self key. To prevent man in the middle attacks, users should make sure the ssh Server's fingerprint, as printed in the connection process, is similar to the one printed here.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.3.4.1.3 |
rlSshClientAuthenticationMethodSpecifies the global authentication method for SSH client. SSH client will apply this authentication method upon connecting to a remote server, if no specific authentication method has been defined for this operation.rw Enumeration .1.3.6.1.4.1.9.6.1.101.78.3.5 |
rlSshClientPasswordSpecifies the global password for SSH client, to be used for 'password' authentication. SSH client will use this password during authentication phase (when connecting remote server), in case no specific password has been specified for this operation. The value of this MIB must not contain charachters ':' or '@' (those are used to indicate parameters seperation in SCP copy). Upon setting the password, its length must be in range 1-70.rw DisplayString .1.3.6.1.4.1.9.6.1.101.78.3.6 |
rlSshClientPasswordChangeTableThis 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. SEQUENCE OF RlSshClientPasswordChangeEntry .1.3.6.1.4.1.9.6.1.101.78.3.7 |
rlSshClientPasswordChangeEntryThe row definition for this table. RlSshClientPasswordChangeEntry .1.3.6.1.4.1.9.6.1.101.78.3.7.1 |
rlSshClientPasswordChangeInetAddrTypeSpecifies the inet address type of remote SCP server InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.6.1.101.78.3.7.1.1 |
rlSshClientPasswordChangeInetAddrSpecifies the inet address of remote SCP server InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.6.1.101.78.3.7.1.2 |
rlSshClientPasswordChangeUsernameSpecifies the username for which the password change is required.rw DisplayString .1.3.6.1.4.1.9.6.1.101.78.3.7.1.3 |
rlSshClientPasswordChangeOldPasswordSpecifies the old password that was in use for rlSshClientPasswordChangeUsername until now. Upon setting a value in this entry, length of this field value must be 6-70. Password of length 0 will always be returned on GET operations.rw DisplayString .1.3.6.1.4.1.9.6.1.101.78.3.7.1.4 |
rlSshClientPasswordChangeNewPasswordSpecifies the new password that should be in use for rlSshClientPasswordChangeUsername from now on. Upon setting a value in this entry, length of this field value must be 6-70. Password of length 0 will always be returned on GET operations.rw DisplayString .1.3.6.1.4.1.9.6.1.101.78.3.7.1.5 |
rlSshClientPasswordChangeStatusSpecifies the status of last password change operation on remote server identified by rlSshClientPasswordChangeInetAddress. In case this data was erased (3 or more password change operations have been performed since the operation on this server), the status will be 'noData'.ro Enumeration .1.3.6.1.4.1.9.6.1.101.78.3.7.1.6 |
rlSshClientPasswordChangeFailureReasonIn case the value of rlSshClientPasswordChangeStatus is 'failed', this field will contain the failure reason.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.3.7.1.7 |
rlSshClientDeleteSelfKeySetting to a value other than 'none' results in deleting the client self key of the chosen type.rw RlSshPublicKeyAlgorithm .1.3.6.1.4.1.9.6.1.101.78.3.8 |
rlSshClientImportExportSelfKeyTableThis 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. SEQUENCE OF RlSshClientImportExportSelfKeyEntry .1.3.6.1.4.1.9.6.1.101.78.3.9 |
rlSshClientImportExportSelfKeyEntryThe row definition for this table. RlSshClientImportExportSelfKeyEntry .1.3.6.1.4.1.9.6.1.101.78.3.9.1 |
rlSshClientImportExportSelfKeyAlgorithmIdentifies the type of key pair. RlSshPublicKeyAlgorithm .1.3.6.1.4.1.9.6.1.101.78.3.9.1.1 |
rlSshClientImportExportSelfKeyFormatSpecifies the format of public/key pair. The following formats are supported for import/export: 1) uuencoded_format - in this format both private and public key are in uu-encoded format, and are seperated from one another by header and footer. An example of the concateneation of all fragments in this format is: -----BEGIN ENCRYPTED RSA PRIVATE KEY----- tDaNkZZoCxXfkLLsLDlZ6T9H8U4Gz637eRV7BYBpapkidAxY1UG0/qgfKLPkbId4wzht6ArV9bE4fMtX wSMOxL3q31pOmUdVhjbWYcgZQBDy1DjFSbuIEdP85c96B9bBE2nPv90mSvb/6j8R2NItT/KJeiYMtLtI N3m6/zESKJGIrX0jP1RFDjVZSS5chSAFgB0egsLZEyOQn7jAqpX/x/easD2J6F/OjPXlJ9Hff2tMb3NU QYyBoWH2J9IxhWB6Vo66R9Y04JGR18uL/rV2sMCtpg5ppkVTEpNTp9qE1yXocR2NmzUfNFap+GJ4IHj8 CzkVfmJM/kEWaJsYgHbAgLyRg4QVyelfobv1B71aQ+u1z9KGu/QajkWdR04OQfsGOL1CvU2LGYDcRjfH jv+jl/UkDRRjoD9kt2WvouT+OL6esvKl0OJBqWbGNXg9TWv/VLtJIwgUno+MLaJuOM4Fh44+wpnqUXwQ TFtBFc8pzt5BoOwbv9gXpicTkq4/+GhwXWXxSVFebKhnHAvKSLT+Ba7K7ZeR8EIIxbXdDNFOiS45R2KI jxxXLXK44u6KGl5MygCKXUOFlJ+Zhgrq6ZH17z/RVJQ2CWqb5Ekn9GY3kH9QZ3mb4MDPfriWi2lHGXHY JmJd4SLQhpBdnOS5tu84QmyU3dNbAdzghDsR+dEY/6g7Cn0kcVkeHNZ0H+mCZik5f6XBD8eplkk43bdR FrkwTeAjwurGcKwdiKkR4DlfSq3DKssVBucTqUpqsKqPXLwTIL44rWKhEPXgGPB2XDG0VLvIRKkAgEGI LNTwOm091Ro= -----END RSA PRIVATE KEY----- -----BEGIN RSA PUBLIC KEY----- MIGHAoGBAOeIC9gRg3YaEGGMp3C00qNwLINAEDZV/J4BWM5WnWwCWZyHXDs2XiEmFu0ZONAD4gcT2f2f NNfCBPye39VVuOkKQuSV0MLLX5800LZ4y1BNcPzPZHpnGaCzl7iAjhfj9MolzAh5VRjeiYt0t1um4dm+ q9A4BtfpJqDYxCW9uxd/AgEj -----END RSA PUBLIC KEY----- Enumeration .1.3.6.1.4.1.9.6.1.101.78.3.9.1.2 |
rlSshClientImportExportSelfKeyFragmentIdIdentifies the index of this fragment in the key pair input/output. INTEGER .1.3.6.1.4.1.9.6.1.101.78.3.9.1.3 |
rlSshClientImportExportSelfKeyFragmentTextA part of the readable text entry for the key pair input/output.rw OCTET STRING .1.3.6.1.4.1.9.6.1.101.78.3.9.1.4 |
rlSshClientRemoteServerPublicKeyFingerprintTableTable 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. SEQUENCE OF RlSshClientRemoteServerPublicKeyFingerprintEntry .1.3.6.1.4.1.9.6.1.101.78.3.10 |
rlSshClientRemoteServerPublicKeyFingerprintEntryThe row definition for this table. RlSshClientRemoteServerPublicKeyFingerprintEntry .1.3.6.1.4.1.9.6.1.101.78.3.10.1 |
rlSshClientRemoteServerFingerprintInetAddrTypeRemote server inet address type. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.6.1.101.78.3.10.1.1 |
rlSshClientRemoteServerFingerprintInetAddrRemote server inet address. InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.6.1.101.78.3.10.1.2 |
rlSshClientRemoteServerFingerprintRemote server fingerprint.rw OCTET STRING .1.3.6.1.4.1.9.6.1.101.78.3.10.1.3 |
rlSshClientRemoteServerFingerprintStatusRow status for this row.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.6.1.101.78.3.10.1.4 |
rlSshClientRemoteServersAuthenticationEnableSetting this field to 'enable' enables remote servers authentication. As a result, while opening a session with a remote server, the fingerprint of the remote server will be computed and looked for in the table rlSshClientRemoteServerPublicKeyFingerprintTable. If an entry with the key (server-inet-address, server-fingerprint) is found, the server is considered authenticated. Otherwise, the server is not authenticated (unless the user specifically approved this server can be trusted).rw Enumeration .1.3.6.1.4.1.9.6.1.101.78.3.11 |
rlSshClientDefaultKeyFlagThis scalar indicates which of the SSH client keys are default keys (automatically generated).ro Enumeration .1.3.6.1.4.1.9.6.1.101.78.3.12 |