RFC 8332: Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) Protocol
In plain English — editorial summary, not part of the RFC
This memo updates RFCs 4252 and 4253 to define new public key algorithms for use of RSA keys with SHA-256 and SHA-512 for server and client authentication in SSH connections.
Document record
- Document ID
- RFC8332
- Published
- March 2018
- Authors
- D. Bider
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7427Signature Authentication in the Internet Key Exchange Version 2 (IKEv2)Current
January 2015
- RFC 8292Voluntary Application Server Identification (VAPID) for Web PushCurrent
November 2017
- RFC 6287OCRA: OATH Challenge-Response AlgorithmCurrent
June 2011
- RFC 4686Analysis of Threats Motivating DomainKeys Identified Mail (DKIM)Current
September 2006
- RFC 3008Domain Name System Security (DNSSEC) Signing AuthorityObsoleted
November 2000
- RFC 8308Extension Negotiation in the Secure Shell (SSH) ProtocolUpdated
March 2018
- RFC 8446The Transport Layer Security (TLS) Protocol Version 1.3Obsoleted
August 2018
- RFC 8121Mutual Authentication Protocol for HTTP: Cryptographic Algorithms Based on the Key Agreement Mechanism 3 (KAM3)Current
April 2017
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?