RFC 4251: The Secure Shell (SSH) Protocol Architecture
In plain English — editorial summary, not part of the RFC
The Secure Shell (SSH) Protocol is a protocol for secure remote login and other secure network services over an insecure network. This document describes the architecture of the SSH protocol, as well as the notation and terminology used in SSH protocol documents. It also discusses the SSH algorithm naming system that allows local extensions. The SSH protocol consists of three major components: The Transport Layer Protocol provides server authentication, confidentiality, and integrity with perfect forward secrecy. The User Authentication Protocol authenticates the client to the server. The Connection Protocol multiplexes the encrypted tunnel into several logical channels. Details of these protocols are described in separate documents. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4251
- Published
- January 2006
- Authors
- T. Ylonen; C. Lonvick
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 30
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4250The Secure Shell (SSH) Protocol Assigned NumbersUpdated
January 2006
- RFC 4252The Secure Shell (SSH) Authentication ProtocolUpdated
January 2006
- RFC 4253The Secure Shell (SSH) Transport Layer ProtocolUpdated
January 2006
- RFC 4254The Secure Shell (SSH) Connection ProtocolUpdated
January 2006
- RFC 4256Generic Message Exchange Authentication for the Secure Shell Protocol (SSH)Current
January 2006
- RFC 4255Using DNS to Securely Publish Secure Shell (SSH) Key FingerprintsCurrent
January 2006
- RFC 4262X.509 Certificate Extension for Secure/Multipurpose Internet Mail Extensions (S/MIME) CapabilitiesCurrent
December 2005
- RFC 4279Pre-Shared Key Ciphersuites for Transport Layer Security (TLS)Updated
December 2005
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?