RFC 4255: Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints
In plain English — editorial summary, not part of the RFC
This document describes a method of verifying Secure Shell (SSH) host keys using Domain Name System Security (DNSSEC). The document defines a new DNS resource record that contains a standard SSH key fingerprint. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4255
- Published
- January 2006
- Authors
- J. Schlyter; W. Griffin
- 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 4035Protocol Modifications for the DNS Security ExtensionsUpdated
March 2005
- RFC 4034Resource Records for the DNS Security ExtensionsUpdated
March 2005
- RFC 4033DNS Security Introduction and RequirementsUpdated
March 2005
- RFC 3007Secure Domain Name System (DNS) Dynamic UpdateCurrent
November 2000
- RFC 2540Detached Domain Name System (DNS) InformationCurrent
March 1999
- RFC 2539Storage of Diffie-Hellman Keys in the Domain Name System (DNS)Updated
March 1999
- RFC 6698The DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSAUpdated
August 2012
- RFC 6844DNS Certification Authority Authorization (CAA) Resource RecordObsoleted
January 2013
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?