RFC 4419: Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol
In plain English — editorial summary, not part of the RFC
This memo describes a new key exchange method for the Secure Shell (SSH) protocol. It allows the SSH server to propose new groups on which to perform the Diffie-Hellman key exchange to the client. The proposed groups need not be fixed and can change with time. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4419
- Published
- March 2006
- Authors
- M. Friedl; N. Provos; W. Simpson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 10
- Also known as
- —
- Updated by:
- RFC 8270
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 4422Simple Authentication and Security Layer (SASL)Current
June 2006
- RFC 4430Kerberized Internet Negotiation of Keys (KINK)Current
March 2006
- RFC 4402A Pseudo-Random Function (PRF) for the Kerberos V Generic Security Service Application Program Interface (GSS-API) MechanismObsoleted
February 2006
- RFC 4401A Pseudo-Random Function (PRF) API Extension for the Generic Security Service Application Program Interface (GSS-API)Current
February 2006
- RFC 4442Bootstrapping Timed Efficient Stream Loss-Tolerant Authentication (TESLA)Current
March 2006
- RFC 4387Internet X.509 Public Key Infrastructure Operational Protocols: Certificate Store Access via HTTPUpdated
February 2006
- RFC 4386Internet X.509 Public Key Infrastructure Repository Locator ServiceUpdated
February 2006
- RFC 4383The Use of Timed Efficient Stream Loss-Tolerant Authentication (TESLA) in the Secure Real-time Transport Protocol (SRTP)Current
February 2006
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?