RFC 4254: The Secure Shell (SSH) Connection Protocol
In plain English — editorial summary, not part of the RFC
Secure Shell (SSH) is a protocol for secure remote login and other secure network services over an insecure network. This document describes the SSH Connection Protocol. It provides interactive login sessions, remote execution of commands, forwarded TCP/IP connections, and forwarded X11 connections. All of these channels are multiplexed into a single encrypted tunnel. The SSH Connection Protocol has been designed to run on top of the SSH transport layer and user authentication protocols. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4254
- Published
- January 2006
- Authors
- T. Ylonen; C. Lonvick
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 24
- Also known as
- —
- Updated by:
- RFC 8308
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4253The Secure Shell (SSH) Transport Layer ProtocolUpdated
January 2006
- RFC 4256Generic Message Exchange Authentication for the Secure Shell Protocol (SSH)Current
January 2006
- RFC 4252The Secure Shell (SSH) Authentication ProtocolUpdated
January 2006
- RFC 4251The Secure Shell (SSH) Protocol ArchitectureUpdated
January 2006
- RFC 4250The Secure Shell (SSH) Protocol Assigned NumbersUpdated
January 2006
- RFC 3836Requirements for Open Pluggable Edge Services (OPES) Callout ProtocolsCurrent
August 2004
- 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
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?