FREE & OPEN
THE OPEN PROTOCOL PLAYGROUND

Make every packet make sense.

Explore the conversations that connect our world. One packet at a time.

66 protocolsZero paywalls. Endless curiosity.

SSH

Web & applicationIntermediate

Negotiate keys, authenticate a user and open a channel.

SIMULATION01 / 04
Loading topology…
0.0s / 4.2s
01
STEP 1 OF 4Client → Server / peer

Identification exchange

Both endpoints send an SSH version identification before binary packets.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20Identification exchange
1.400198.51.100.20192.0.2.10KEXINIT + key exchange
2.800192.0.2.10198.51.100.20NEWKEYS + user authentication
4.200198.51.100.20192.0.2.10Channel open confirmation

Negotiate keys, authenticate a user and open a channel.

Explain Identification exchange and distinguish it from Channel open confirmation.

Prerequisites: Ethernet

Ready to test your understanding?

Rebuild the exchange. Read the fields. Find the mistakes.

Learn from the sourceRFC 4253Protocol guide

SSH: protocol guide / panduan protokol

Negotiate keys, authenticate a user and open a channel.

Negosiasikan kunci, autentikasi pengguna, dan buka kanal.

Communication walkthrough / Alur komunikasi

  1. Identification exchange

    Both endpoints send an SSH version identification before binary packets.

    Kedua endpoint mengirim identifikasi versi SSH sebelum paket biner.

  2. KEXINIT + key exchange

    Algorithm negotiation and key exchange authenticate the server host key.

    Negosiasi algoritma dan pertukaran kunci mengautentikasi host key server.

  3. NEWKEYS + user authentication

    After both NEWKEYS messages, encrypted user authentication can proceed.

    Setelah kedua pesan NEWKEYS, autentikasi pengguna terenkripsi dapat berlangsung.

  4. Channel open confirmation

    An authenticated session may open a shell or other channel.

    Sesi terautentikasi dapat membuka shell atau kanal lain.

Source and simulation scope

This is a simplified, deterministic teaching scenario. Timing is illustrative. Messages grouped within one event are explicitly condensed. Hexadecimal fixtures, where shown, contain only the indicated protocol ADU, not a full network capture. No PCAP files are supplied.

RFC 4253 ↗