Visual RFC.
ALL RFCs / RFC 4251
Read the RFC ↗
RFC 4251 / MECHANISMS

Security has endpoint limits

05

The encrypted tunnel cannot protect data after a compromised endpoint receives it.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

RFC 4251 · § 9.5.1EXAMPLE
3 / 3
Security has endpoint limitsThe encrypted tunnel cannot protect data after a compromised endpoint receives it. Current state: Visible traffic shape.Security has endpoint limitsClientEndpointencrypted transportplaintext heretiming / volume remain visibleTransport security does not repair a compromised endpoint.
03
Visible traffic shape

An observer may still see traffic timing and approximate size.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

The security of endpoints is outside what the transport cipher alone can provide.

  • The security of endpoints is outside what the transport cipher alone can provide.
  • Forwarding can expose services through the tunnel.
  • Traffic analysis can still reveal timing and volume information.
DETAILS

The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. Three layers have different jobs
  2. Host keys identify the server
  3. An unchecked key enables a middleman
  4. One transport carries channels
  5. Security has endpoint limits
RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗