RFC 4716: The Secure Shell (SSH) Public Key File Format
In plain English — editorial summary, not part of the RFC
This document formally documents an existing public key file format in use for exchanging public keys between different Secure Shell (SSH) implementations. In addition, this document defines a standard textual representation for SSH public key fingerprints. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4716
- Published
- November 2006
- Authors
- J. Galbraith; R. Thayer
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- sec
- Pages
- 10
- Also known as
- —
- Updated by:
- RFC 9519
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 4738MIKEY-RSA-R: An Additional Mode of Key Distribution in Multimedia Internet KEYing (MIKEY)Current
November 2006
- RFC 4683Internet X.509 Public Key Infrastructure Subject Identification Method (SIM)Current
October 2006
- RFC 4752The Kerberos V5 ("GSSAPI") Simple Authentication and Security Layer (SASL) MechanismCurrent
November 2006
- RFC 4675RADIUS Attributes for Virtual LAN and Priority SupportCurrent
September 2006
- RFC 4673RADIUS Dynamic Authorization Server MIBCurrent
September 2006
- RFC 4672RADIUS Dynamic Authorization Client MIBCurrent
September 2006
- RFC 4671RADIUS Accounting Server MIB for IPv6Current
August 2006
- RFC 4670RADIUS Accounting Client MIB for IPv6Current
August 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?