SSH (Secure Shell) is a cryptographic network protocol that provides secure remote login and command execution over an unsecured network. It operates in three layers: the Transport Layer Protocol (establishes an encrypted tunnel over TCP, typically port 22), the User Authentication Protocol (authenticates users via password or public-key methods), and the Connection Protocol (provides interactive sessions, remote command execution, and connection forwarding).
SSH uses public-key cryptography for authentication, meaning a user holds a private key while the remote server stores the corresponding public key. When connecting, the server verifies the client's private key against the stored public key, avoiding the need to send passwords over the network.
Example:
On a cloud server (AWS EC2, Google Cloud, or Azure), you provision an instance with an SSH key pair. The public key is injected into ~/.ssh/authorized_keys on the instance. You then connect locally with:
ssh -i mykey.pem ubuntu@203.0.113.45
SSH authenticates using your private key and grants you a secure shell session.
Port and Standards: SSH defaults to port 22 and is standardized in IETF RFCs 4250–4254 (the Secsh protocol suite, published 2006).
WarningIf you see "REMOTE HOST IDENTIFICATION HAS CHANGED," do not blindly delete your
known_hostsentry. This warning protects against man-in-the-middle attacks. Investigate why the host key changed (e.g., server rebuild, DNS hijacking) before proceeding. Ignoring it defeats SSH's server-authentication guarantee.
Guides that use this term
Related terms
New articles, straight to your inbox
I’d like to receive product updates and new articles from InfraNest by email. I can unsubscribe at any time. Privacy policy