RFC 4344: The Secure Shell (SSH) Transport Layer Encryption Modes

In plain English — editorial summary, not part of the RFC

Researchers have discovered that the authenticated encryption portion of the current SSH Transport Protocol is vulnerable to several attacks. This document describes new symmetric encryption methods for the Secure Shell (SSH) Transport Protocol and gives specific recommendations on how frequently SSH implementations should rekey. [STANDARDS-TRACK]

Document record

Document ID

RFC4344

Published

January 2006

Authors

M. Bellare; T. Kohno; C. Namprempre

Status

PROPOSED STANDARD

Stream

IETF

Area

sec

Pages

12

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC4344

Topics

• rekey

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 4346The Transport Layer Security (TLS) Protocol Version 1.1Obsoleted

  April 2006

• RFC 4335The Secure Shell (SSH) Session Channel Break ExtensionCurrent

  January 2006

• RFC 4334Certificate Extensions and Attributes Supporting Authentication in Point-to-Point Protocol (PPP) and Wireless Local Area Networks (WLAN)Current

  February 2006

• RFC 4359The Use of RSA/SHA-1 Signatures within Encapsulating Security Payload (ESP) and Authentication Header (AH)Current

  January 2006

• RFC 4325Internet X.509 Public Key Infrastructure Authority Information Access Certificate Revocation List (CRL) ExtensionObsoleted

  December 2005

• RFC 4366Transport Layer Security (TLS) ExtensionsObsoleted

  April 2006

• RFC 4372Chargeable User IdentityCurrent

  January 2006

• RFC 4309Using Advanced Encryption Standard (AES) CCM Mode with IPsec Encapsulating Security Payload (ESP)Current

  December 2005

Also filed under

• PROPOSED STANDARD
• 2006
• IETF stream
• sec area