RFC 4256 on Generic Message Exchange Authentication for the Secure Shell Protocol (SSH)

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

        RFC 4256

        Title:      Generic Message Exchange Authentication for
                    the Secure Shell Protocol (SSH)
        Author(s):  F. Cusack, M. Forssen
        Status:     Standards Track
        Date:       January 2006
        Mailbox:    frank@savecore.net, maf@appgate.com
        Pages:      12
        Characters: 24728
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-secsh-auth-kbdinteract-07.txt

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

The Secure Shell Protocol (SSH) is a protocol for secure remote login
and other secure network services over an insecure network.  This
document describes a general purpose authentication method for the SSH
protocol, suitable for interactive authentications where the
authentication data should be entered via a keyboard (or equivalent
alphanumeric input device).  The major goal of this method is to allow
the SSH client to support a whole class of authentication mechanism(s)
without knowing the specifics of the actual authentication mechanism(s).

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.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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

        To: rfc-info@RFC-EDITOR.ORG
        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.  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.  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.