OID reference

rlSshServerHostPublicKeyTable

1.3.6.1.4.1.89.78.2.1

Description

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…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.89.78.2 (rlSshServer)
Node code
1
Node name
rlSshServerHostPublicKeyTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.89.78.2.1
URN notation
urn:oid:1.3.6.1.4.1.89.78.2.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
SEQUENCE OF RlSshServerHostPublicKeyTableEntry
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

rlSshServerHostPublicKeyTable · current

rlSshServerHostPublicKeyTable OBJECT-TYPE
   SYNTAX SEQUENCE OF RlSshServerHostPublicKeyTableEntry
   MAX-ACCESS   not-accessible
   STATUS       current
   DESCRIPTION
    "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"
    ::= { rlSshServer 1 }

rlSshServerHostPublicKeyTable · current

rlSshServerHostPublicKeyTable OBJECT-TYPE
   SYNTAX SEQUENCE OF RlSshServerHostPublicKeyTableEntry
   MAX-ACCESS   not-accessible
   STATUS       current
   DESCRIPTION
    "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"
    ::= { rlSshServer 1 }

Meaning

Descriptions

1 unique

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

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

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

rlSshServerHostPublicKeyTable · 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: rlSshServerHostPublicKeyTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "rlSshServerHostPublicKeyTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "RlSshServerHostPublicKeyTableEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"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\"",
    "::=",
    "{",
    "rlSshServer",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "RlSshServerHostPublicKeyTableEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "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"
    ],
    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.2.1.1 rlSshServerHostPublicKeyTableEntry33

Siblings (14)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.89.78.2.2 rlSshServerHostPublicKeyFingerprintTable14
1.3.6.1.4.1.89.78.2.3 rlSshServerAuthorizedUsersPublicKeyTable15
1.3.6.1.4.1.89.78.2.5 rlSshServerAuthorizedUsersPublicKeyFingerprintTable15
1.3.6.1.4.1.89.78.2.6 rlSshServerSessionTable18
1.3.6.1.4.1.89.78.2.7 rlSshServerSessionInetTable19
1.3.6.1.4.1.89.78.2.8 rlSshServerImportExportSelfKeyTable15
1.3.6.1.4.1.89.78.2.101 rlSshServerPort00
1.3.6.1.4.1.89.78.2.102 rlSshServerEnable00
1.3.6.1.4.1.89.78.2.103 rlSshServerEnablePublicKeyAuthentication00
1.3.6.1.4.1.89.78.2.104 rlSshServerRegenerateHostKey00
1.3.6.1.4.1.89.78.2.105 rlSshServerDefaultKeyFlag00
1.3.6.1.4.1.89.78.2.106 rlSshServerDeleteSelfKey00
1.3.6.1.4.1.89.78.2.107 rlSshServerEnablePublicKeyAuthAutoLogin00
1.3.6.1.4.1.89.78.2.108 rlSshServerEnablePasswordAuthentication00