OID reference

rlSshClientSelfPublicKeyTable

1.3.6.1.4.1.89.78.3.3

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 t…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.89.78.3 (rlSshClient)
Node code
3
Node name
rlSshClientSelfPublicKeyTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.89.78.3.3
URN notation
urn:oid:1.3.6.1.4.1.89.78.3.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 89 78 3 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) rnd(89) rlSsh(78) rlSshClient(3) rlSshClientSelfPublicKeyTable(3)}
OID-IRI notation
  • /1/3/6/1/4/1/89/78/3/3
  • /ISO/Identified-Organization/6/1/4/1/89/78/3/3
  • /ISO/3/6/1/4/1/89/78/3/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable
  • /iso/identified-organization/dod/internet/private/enterprises/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable
  • /iso/org/dod/internet/private/enterprise/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable
  • /iso/org/dod/internet/private/enterprises/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable
  • /iso/org/dod/internet/private/ldap-enterprise/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable
  • /iso/org/dod/internet/private/vendor-objects/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable
  • /iso/iso-identified-organization/dod/internet/private/enterprise/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable
  • /iso/iso-identified-organization/dod/internet/private/enterprises/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable
  • /iso/iso-organization/dod/internet/private/enterprise/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable
  • /iso/iso-organization/dod/internet/private/enterprises/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable
  • /iso/iso-organization/dod/internet/private/vendor-objects/rnd/rlSsh/rlSshClient/rlSshClientSelfPublicKeyTable

SNMP properties

Value type
SEQUENCE OF RlSshClientSelfPublicKeyTableEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Product context

Documented MIB packages

The NETGEAR catalogue lists MIB files containing this definition with these product and release labels:

These are catalogue release labels, not necessarily MIB revisions. A MIB definition does not establish that a device implements it or permits access.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

rlSshClientSelfPublicKeyTable · current

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 }

rlSshClientSelfPublicKeyTable · current

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 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

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

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Dell MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copiesNETGEAR official product and EOL MIB downloads

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Dell MIB copies (LibreNMS/Observium Community), and others1 record · 5 sources

Description 1

rlSshClientSelfPublicKeyTable · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Dell MIB copies (LibreNMS/Observium Community), and others5 sources

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
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.89)

Nethaniel Rina

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.89.78.3.3.1 rlSshClientSelfPublicKeyTableEntry33

Siblings (11)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.89.78.3.1 rlSshClientUserName00
1.3.6.1.4.1.89.78.3.2 rlSshClientRegenerateSelfKey00
1.3.6.1.4.1.89.78.3.4 rlSshClientSelfPublicKeyFingerprintTable14
1.3.6.1.4.1.89.78.3.5 rlSshClientAuthenticationMethod00
1.3.6.1.4.1.89.78.3.6 rlSshClientPassword00
1.3.6.1.4.1.89.78.3.7 rlSshClientPasswordChangeTable18
1.3.6.1.4.1.89.78.3.8 rlSshClientDeleteSelfKey00
1.3.6.1.4.1.89.78.3.9 rlSshClientImportExportSelfKeyTable15
1.3.6.1.4.1.89.78.3.10 rlSshClientRemoteServerPublicKeyFingerprintTable15
1.3.6.1.4.1.89.78.3.11 rlSshClientRemoteServersAuthenticationEnable00
1.3.6.1.4.1.89.78.3.12 rlSshClientDefaultKeyFlag00