RFC 4255 on Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints

[rfc-editor%rfc-editor.org@localhost]

A new Request for Comments is now available in online RFC libraries.


        RFC 4255

        Title:      Using DNS to Securely Publish Secure Shell (SSH)
                    Key Fingerprints
        Author(s):  J. Schlyter, W. Griffin
        Status:     Standards Track
        Date:       January 2006
        Mailbox:    jakob%openssh.com@localhost, wgriffin%sparta.com@localhost
        Pages:      9
        Characters: 18399
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-secsh-dns-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4255.txt


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.

This document is a product of the Secure Shell Working Group of the
IETF. 

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST%IETF.ORG@localhost.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST%RFC-EDITOR.ORG@localhost.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info%RFC-EDITOR.ORG@localhost with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info%RFC-EDITOR.ORG@localhost
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager%RFC-EDITOR.ORG@localhost.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR%RFC-EDITOR.ORG@localhost.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.

<ftp://ftp.isi.edu/in-notes/rfc4255.txt>