SSH KEXINIT message
E901637
The SSH KEXINIT message is a protocol packet used during SSH session setup to exchange and negotiate key exchange, encryption, and other security-related algorithms between client and server.
All labels observed (1)
| Label | Occurrences |
|---|---|
| SSH KEXINIT message canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T11033338 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: SSH KEXINIT message Context triple: [SSH Encryption Algorithm Names, negotiatedVia, SSH KEXINIT message]
-
A.
SSH_MSG_REQUEST_FAILURE
SSH_MSG_REQUEST_FAILURE is an SSH protocol message type indicating that a previously sent global request has been denied or could not be fulfilled.
-
B.
SSH Message Numbers
SSH Message Numbers is an IANA-maintained registry that assigns and documents numeric codes used to identify different message types in the Secure Shell (SSH) protocol.
-
C.
SSH_MSG_GLOBAL_REQUEST
SSH_MSG_GLOBAL_REQUEST is an SSH protocol message type used by a client or server to request various global actions, such as TCP/IP port forwarding or other session-wide operations.
-
D.
SSH Communications Security
SSH Communications Security is a Finnish cybersecurity company best known for developing and commercializing the Secure Shell (SSH) protocol and related secure communications solutions.
-
E.
SSH_MSG_USERAUTH_SUCCESS
SSH_MSG_USERAUTH_SUCCESS is an SSH protocol message indicating that a user's authentication has completed successfully, as specified in RFC 4252.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: SSH KEXINIT message Target entity description: The SSH KEXINIT message is a protocol packet used during SSH session setup to exchange and negotiate key exchange, encryption, and other security-related algorithms between client and server.
-
A.
SSH_MSG_REQUEST_FAILURE
SSH_MSG_REQUEST_FAILURE is an SSH protocol message type indicating that a previously sent global request has been denied or could not be fulfilled.
-
B.
SSH Message Numbers
SSH Message Numbers is an IANA-maintained registry that assigns and documents numeric codes used to identify different message types in the Secure Shell (SSH) protocol.
-
C.
SSH_MSG_GLOBAL_REQUEST
SSH_MSG_GLOBAL_REQUEST is an SSH protocol message type used by a client or server to request various global actions, such as TCP/IP port forwarding or other session-wide operations.
-
D.
SSH Communications Security
SSH Communications Security is a Finnish cybersecurity company best known for developing and commercializing the Secure Shell (SSH) protocol and related secure communications solutions.
-
E.
SSH_MSG_USERAUTH_SUCCESS
SSH_MSG_USERAUTH_SUCCESS is an SSH protocol message indicating that a user's authentication has completed successfully, as specified in RFC 4252.
- F. None of above. chosen
Statements (49)
| Predicate | Object |
|---|---|
| instanceOf |
SSH protocol message
ⓘ
key exchange negotiation packet ⓘ |
| algorithmListsFormat | comma-separated name-lists ⓘ |
| containsField |
compression_algorithms_client_to_server
ⓘ
compression_algorithms_server_to_client ⓘ cookie ⓘ encryption_algorithms_client_to_server ⓘ encryption_algorithms_server_to_client ⓘ first_kex_packet_follows ⓘ kex_algorithms ⓘ languages_client_to_server ⓘ languages_server_to_client ⓘ mac_algorithms_client_to_server ⓘ mac_algorithms_server_to_client ⓘ reserved ⓘ server_host_key_algorithms ⓘ |
| cookiePurpose | randomness to thwart certain attacks ⓘ |
| definedIn | RFC 4253 NERFINISHED ⓘ |
| directionality | symmetric between client and server ⓘ |
| hasCookieLength | 16 bytes GENERATED ⓘ |
| hasMessageNumber | 20 ⓘ |
| mayBeRepeated | yes, when rekeying ⓘ |
| messageNameInRFC4253 | SSH_MSG_KEXINIT NERFINISHED ⓘ |
| negotiationRule | first algorithm in client list that also appears in server list is chosen ⓘ |
| occursBefore |
channel establishment
ⓘ
user authentication ⓘ |
| partOf | Secure Shell (SSH) protocol NERFINISHED ⓘ |
| precedes |
NEWKEYS message
ⓘ
SSH key exchange messages ⓘ |
| purpose |
exchange algorithm capability lists
ⓘ
negotiate compression algorithms ⓘ negotiate encryption algorithms ⓘ negotiate key exchange algorithms ⓘ negotiate language preferences ⓘ negotiate message authentication algorithms ⓘ |
| relatedTo |
SSH transport layer encryption
ⓘ
SSH_MSG_NEWKEYS ⓘ |
| securityRole |
establish cryptographic parameters
ⓘ
prevent downgrade attacks via explicit algorithm lists ⓘ |
| sentBy |
SSH client
ⓘ
SSH server ⓘ |
| sentOver | already established TCP connection ⓘ |
| standardizedBy |
Internet Engineering Task Force
ⓘ
surface form:
IETF
|
| transportLayer | SSH transport layer protocol ⓘ |
| triggeredBy | start of SSH key exchange ⓘ |
| usedDuring |
SSH key exchange phase
ⓘ
SSH session setup ⓘ |
| usedFor | rekeying negotiation ⓘ |
| usedIn | SSH-2 NERFINISHED ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: SSH KEXINIT message Description of subject: The SSH KEXINIT message is a protocol packet used during SSH session setup to exchange and negotiate key exchange, encryption, and other security-related algorithms between client and server.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.