Status in source: current.
Names: rlSshClientSelfPublicKeyTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rlSshClientSelfPublicKeyTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"RlSshClientSelfPublicKeyTableEntry",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"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\"",
"::=",
"{",
"rlSshClient",
"3",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"RlSshClientSelfPublicKeyTableEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"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"
],
null,
null,
null,
null
]
}