SSH
— Secure ShellSSH replaced insecure cleartext terminal protocols like Telnet and rlogin. It provides strong public-key authentication, encrypted remote shell sessions, secure file transfer (SFTP/SCP), and encrypted TCP port tunneling.
Interactive Session: How SSH Works
Step through the packet exchange sequence between nodes.
Interactive Execution Sandbox
Interact with a live or clearly-labelled simulated instance of SSH.
Threat Model & Attack Simulation
How this protocol is attacked in practice, what defenders can see, and which control stops it.
Threat model & attack simulation
SimulatedDefensive education. Every step runs in this page; no traffic is generated or sent.
Credential brute force
Credential attackAutomated guessing against exposed SSH services eventually finds a weak password.
Enumerate the service
The attacker confirms SSH and its version without triggering alarms.
Repeated banner grabs and version scans.
Remote code execution with the victim account privileges.
Defences that matter
- Disable password authentication; use keys
- MFA and source-address restrictions
- Fail2ban and login alerting
This is a conceptual model for defenders, not an exploit toolkit. It contains no payloads, tooling or instructions for attacking systems you do not own.
Protocol Specification & Architecture
Key characteristics, real-world deployment patterns, and trade-offs.
Core Technical Features
- Diffie-Hellman cryptographic key exchange
- Public Key (ED25519, RSA) and password authentication
- Secure port forwarding and SOCKS5 proxy tunneling
- Encrypted remote shell execution and SFTP subsystem
Real-World Use Cases
- Remote Linux server administration
- Git over SSH repository push/pull
- Encrypted database port tunneling
Advantages & Strengths
- Industry gold standard for secure server administration
- Strong cryptographic forward secrecy
Limitations & Vulnerabilities
- Requires strict host-key verification to prevent man-in-the-middle on first connect (TOFU model)