RFC 4345 on Improved Arcfour Modes for the Secure Shell (SSH) Transport Layer Protocol

rfc-editor@rfc-editor.org Mon, 23 January 2006 21:53 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F19dN-0006kq-6F; Mon, 23 Jan 2006 16:53:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F19dK-0006ke-H4 for ietf-announce@megatron.ietf.org; Mon, 23 Jan 2006 16:53:54 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24193 for <ietf-announce@ietf.org>; Mon, 23 Jan 2006 16:52:25 -0500 (EST)
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F19mk-0007J2-6q for ietf-announce@ietf.org; Mon, 23 Jan 2006 17:03:38 -0500
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.8/8.12.8) with ESMTP id k0NLrq55010438; Mon, 23 Jan 2006 13:53:52 -0800
Received: (from apache@localhost) by nit.isi.edu (8.12.8/8.12.8/Submit) id k0NLrqj3010437; Mon, 23 Jan 2006 13:53:52 -0800
Date: Mon, 23 Jan 2006 13:53:52 -0800
Message-Id: <200601232153.k0NLrqj3010437@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="d8143b60c1368fc687e364217ab72751"
X-Spam-Score: -12.9 (------------)
X-Scan-Signature: 093efd19b5f651b2707595638f6c4003
Cc: rfc-editor@rfc-editor.org
Subject: RFC 4345 on Improved Arcfour Modes for the Secure Shell (SSH) Transport Layer Protocol
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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


        RFC 4345

        Title:      Improved Arcfour Modes for the 
                    Secure Shell SSH Transport Layer Protocol 
        Author:     B. Harris
        Status:     Standards Track
        Date:       January 2006
        Mailbox:    bjh21@bjh21.me.uk
        Pages:      5
        Characters: 8967
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-harris-ssh-arcfour-fixes-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4345.txt

This document specifies methods of using the Arcfour cipher in the
Secure Shell (SSH) protocol that mitigate the weakness of the
cipher\'s key-scheduling algorithm.  [STANDARDS TRACK].

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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

...

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


        RFC 4345

        Title:      Improved Arcfour Modes for the 
                    Secure Shell SSH Transport Layer Protocol 
        Author:     B. Harris
        Status:     Standards Track
        Date:       January 2006
        Mailbox:    bjh21@bjh21.me.uk
        Pages:      5
        Characters: 8967
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-harris-ssh-arcfour-fixes-03.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4345.txt

This document specifies methods of using the Arcfour cipher in the
Secure Shell (SSH) protocol that mitigate the weakness of the
cipher\'s key-scheduling algorithm.  [STANDARDS TRACK].

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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

...

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce