draft-ietf-curdle-rc4-die-die-die-16.txt   draft-ietf-curdle-rc4-die-die-die-17.txt 
Internet Engineering Task Force L. Camara Internet Engineering Task Force L. Camara
Internet-Draft Internet-Draft
Updates: 4253 (if approved) L. Velvindron Updates: 4253 (if approved) L. Velvindron
Intended status: Best Current Practice cyberstorm.mu Intended status: Best Current Practice cyberstorm.mu
Expires: January 31, 2020 July 30, 2019 Expires: April 23, 2020 October 21, 2019
Deprecating RC4 in Secure Shell (SSH) Deprecating RC4 in Secure Shell (SSH)
draft-ietf-curdle-rc4-die-die-die-16 draft-ietf-curdle-rc4-die-die-die-17
Abstract Abstract
This document deprecates RC4 in Secure Shell (SSH). Therefore, this This document deprecates RC4 in Secure Shell (SSH). Therefore, this
document formally moves to Historic RFC4345. document formally moves RFC4345 to historic status.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 31, 2020. This Internet-Draft will expire on April 23, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 23 skipping to change at page 2, line 23
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4 6. References . . . . . . . . . . . . . . . . . . . . . . . . . 4
6.1. Normative References . . . . . . . . . . . . . . . . . . 4 6.1. Normative References . . . . . . . . . . . . . . . . . . 4
6.2. Informative References . . . . . . . . . . . . . . . . . 4 6.2. Informative References . . . . . . . . . . . . . . . . . 4
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 4
1. Introduction 1. Introduction
The usage of RC4 suites ( also designated as arcfour ) for SSH are The usage of RC4 suites ( also designated as arcfour ) for SSH are
specified in [RFC4253] and [RFC4345]. [RFC4253] specifies the specified in [RFC4253] and [RFC4345]. [RFC4253] specifies the
allocation of the "arcfour" cipher for SSH. [RFC4345] specifies and allocation of the "arcfour" cipher for SSH. [RFC4345] specifies and
allocates the "arcfour-128" and "arcfour-256" ciphers for SSH. RC4 allocates the "arcfour128" and "arcfour256" ciphers for SSH. RC4
encryption has known weaknesses [RFC7465] [RFC8429], and the encryption has known weaknesses [RFC7465] [RFC8429], and the
deprecation process should be begun for their use in Secure Shell deprecation process should be begun for their use in Secure Shell
(SSH) [RFC4253]. Accordingly, [RFC4253] is updated to note the (SSH) [RFC4253]. Accordingly, [RFC4253] is updated to note the
deprecation of the RC4 ciphers and [RFC4345] is moved to Historic as deprecation of the RC4 ciphers and [RFC4345] is moved to Historic as
all ciphers it specifies MUST NOT be used. all ciphers it specifies MUST NOT be used.
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
skipping to change at page 2, line 50 skipping to change at page 2, line 50
[RFC4253] is updated to prohibit arcfour's use in SSH. [RFC4253] [RFC4253] is updated to prohibit arcfour's use in SSH. [RFC4253]
allocates the "arcfour" cipher in Section 6.3 by defining a list of allocates the "arcfour" cipher in Section 6.3 by defining a list of
defined ciphers where the "arcfour" cipher appears as optional as defined ciphers where the "arcfour" cipher appears as optional as
mentioned below: mentioned below:
+---------------+-----------------+---------------------------------+ +---------------+-----------------+---------------------------------+
| arcfour | OPTIONAL | the ARCFOUR stream cipher with | | arcfour | OPTIONAL | the ARCFOUR stream cipher with |
| | | a 128-bit key | | | | a 128-bit key |
+---------------+-----------------+---------------------------------+ +---------------+-----------------+---------------------------------+
The current document updates the status of the "arcfour" ciphers in This current document updates the status of the "arcfour" ciphers in
the list of [RFC4253] Section 6.3 by moving it from OPTIONAL to MUST the list of [RFC4253] Section 6.3 by moving it from OPTIONAL to MUST
NOT. NOT.
+----------+-----------+--------------------------------------------+ +----------+-----------+--------------------------------------------+
| arcfour | MUST NOT | the ARCFOUR stream cipher with a 128-bit | | arcfour | MUST NOT | the ARCFOUR stream cipher with a 128-bit |
| | | key | | | | key |
+----------+-----------+--------------------------------------------+ +----------+-----------+--------------------------------------------+
[RFC4253] defines the "arcfour" ciphers with the text mentioned [RFC4253] defines the "arcfour" ciphers with the text mentioned
below: below:
The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys. The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys.
The Arcfour cipher is compatible with the RC4 cipher [SCHNEIER]. The Arcfour cipher is compatible with the RC4 cipher [SCHNEIER].
Arcfour (and RC4) has problems with weak keys, and should be used Arcfour (and RC4) has problems with weak keys, and should be used
with caution. with caution.
The current document updates [RFC4253] Section 6.3 by replacing the This current document updates [RFC4253] Section 6.3 by replacing the
text above with the following text: text above with the following text:
The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys. The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys.
The Arcfour cipher is compatible with the RC4 cipher [SCHNEIER]. The Arcfour cipher is compatible with the RC4 cipher [SCHNEIER].
Arcfour (and RC4) has known weakenesses [RFC7465] [RFC8429], and MUST Arcfour (and RC4) has known weaknesses [RFC7465] [RFC8429], and MUST
NOT be used. NOT be used.
3. IANA Considerations 3. IANA Considerations
The IANA is requested to update the Encryption Algorithm Name The IANA is requested to update the Encryption Algorithm Name
Registry of the Secure Shell (SSH) Protocol Parameters [IANA]. The Registry of the Secure Shell (SSH) Protocol Parameters [IANA]. The
Registration procedure is IETF Review which is achieved by this Registration procedure is IETF Review which is achieved by this
document. The registry should be updated as follows: document. The registry should be updated as follows:
+------------------------------+------------+------+ +------------------------------+------------+------+
 End of changes. 8 change blocks. 
8 lines changed or deleted 8 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/