draft-ietf-curdle-rc4-die-die-die-11.txt   draft-ietf-curdle-rc4-die-die-die-12.txt 
Internet Engineering Task Force L. Camara Internet Engineering Task Force L. Camara
Internet-Draft Internet-Draft
Obsoletes: 4325 (if approved) L. Velvindron Obsoletes: 4345 (if approved) L. Velvindron
Intended status: Best Current Practice cyberstorm.mu Intended status: Best Current Practice cyberstorm.mu
Expires: April 15, 2019 October 12, 2018 Expires: April 18, 2019 October 15, 2018
Deprecating RC4 in Secure Shell (SSH) Deprecating RC4 in Secure Shell (SSH)
draft-ietf-curdle-rc4-die-die-die-11 draft-ietf-curdle-rc4-die-die-die-12
Abstract Abstract
This document deprecates RC4 in Secure Shell (SSH). Therefore, this This document deprecates RC4 in Secure Shell (SSH). Therefore, this
document formally obsoletes and moves to Historic [RFC4345]. document formally obsoletes and moves to Historic RFC4345.
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 April 15, 2019. This Internet-Draft will expire on April 18, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 11 skipping to change at page 2, line 11
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
2. Updates to RFC 4253 . . . . . . . . . . . . . . . . . . . . . 2 2. Updates to RFC 4253 . . . . . . . . . . . . . . . . . . . . . 2
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 4 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . . . . . . . . . . . . . . . . . . 5 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 the "arcfour-128" and "arcfour-256" ciphers for SSH. allocates the the "arcfour-128" and "arcfour-256" ciphers for SSH.
RC4 encryption is steadily weakening in cryptographic strength RC4 encryption is steadily weakening in cryptographic strength
[RFC7465] [I-D.ietf-curdle-des-des-des-die-die-die], and the [RFC7465] [I-D.ietf-curdle-des-des-des-die-die-die], and the
deprecation process should be begun for their use in Secure Shell deprecation process should be begun for their use in Secure Shell
skipping to change at page 3, line 44 skipping to change at page 3, line 44
+-------------+------------------------------------+ +-------------+------------------------------------+
| Encryption | Algorithm Name Reference Note | | Encryption | Algorithm Name Reference Note |
+-------------+------------------------------------+ +-------------+------------------------------------+
| arcfour | [RFC-TBD] | | arcfour | [RFC-TBD] |
| arcfour128 | [RFC-TBD] | | arcfour128 | [RFC-TBD] |
| arcfour256 | [RFC-TBD] | | arcfour256 | [RFC-TBD] |
+-------------+------------------------------------+ +-------------+------------------------------------+
Where TBD is the RFC number assigned to the document. Where TBD is the RFC number assigned to the document.
All drafts are required to have an IANA considerations section (see
Guidelines for Writing an IANA Considerations Section in RFCs
[RFC5226] for a guide). If the draft does not require IANA to do
anything, the section contains an explicit statement that this is the
case (as above). If there are no requirements for IANA, the section
will be removed during conversion into an RFC by the RFC Editor.
4. Acknowledgements 4. Acknowledgements
The authors would like to thank Daniel Migault and Rich Salz. The authors would like to thank Daniel Migault and Rich Salz.
5. Security Considerations 5. Security Considerations
This document only prohibits the use of RC4 in SSH, and introduces no This document only prohibits the use of RC4 in SSH, and introduces no
new security considerations. new security considerations.
6. References 6. References
6.1. Normative References 6.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[SCHNEIER]
Schneier, B., "Applied Cryptography Second Edition:
protocols algorithms and source in code in C", , 1996,
<SCHNEIER>.
6.2. Informative References 6.2. Informative References
[I-D.ietf-curdle-des-des-des-die-die-die] [I-D.ietf-curdle-des-des-des-die-die-die]
Kaduk, B. and M. Short, "Deprecate 3DES and RC4 in Kaduk, B. and M. Short, "Deprecate 3DES and RC4 in
Kerberos", draft-ietf-curdle-des-des-des-die-die-die-05 Kerberos", draft-ietf-curdle-des-des-des-die-die-die-05
(work in progress), September 2017. (work in progress), September 2017.
[IANA] "Secure Shell (SSH) Protocol Parameters: Encryption
Algorithm Names", <https://www.iana.org/assignments/ssh-
parameters/ssh-parameters.xhtml#ssh-parameters-17>.
[RFC4253] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH) [RFC4253] Ylonen, T. and C. Lonvick, Ed., "The Secure Shell (SSH)
Transport Layer Protocol", RFC 4253, DOI 10.17487/RFC4253, Transport Layer Protocol", RFC 4253, DOI 10.17487/RFC4253,
January 2006, <https://www.rfc-editor.org/info/rfc4253>. January 2006, <https://www.rfc-editor.org/info/rfc4253>.
[RFC4345] Harris, B., "Improved Arcfour Modes for the Secure Shell [RFC4345] Harris, B., "Improved Arcfour Modes for the Secure Shell
(SSH) Transport Layer Protocol", RFC 4345, (SSH) Transport Layer Protocol", RFC 4345,
DOI 10.17487/RFC4345, January 2006, DOI 10.17487/RFC4345, January 2006,
<https://www.rfc-editor.org/info/rfc4345>. <https://www.rfc-editor.org/info/rfc4345>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", RFC 5226,
DOI 10.17487/RFC5226, May 2008,
<https://www.rfc-editor.org/info/rfc5226>.
[RFC7465] Popov, A., "Prohibiting RC4 Cipher Suites", RFC 7465, [RFC7465] Popov, A., "Prohibiting RC4 Cipher Suites", RFC 7465,
DOI 10.17487/RFC7465, February 2015, DOI 10.17487/RFC7465, February 2015,
<https://www.rfc-editor.org/info/rfc7465>. <https://www.rfc-editor.org/info/rfc7465>.
[SCHNEIER]
Schneier, B., "Applied Cryptography Second Edition:
protocols algorithms and source in code in C", , 1996,
<SCHNEIER>.
Authors' Addresses Authors' Addresses
Luis Camara Luis Camara
Email: luis.camara@live.com.pt Email: luis.camara@live.com.pt
Loganaden Velvindron Loganaden Velvindron
cyberstorm.mu cyberstorm.mu
Mauritius Mauritius
Email: loganaden@gmail.com Email: loganaden@gmail.com
 End of changes. 13 change blocks. 
26 lines changed or deleted 17 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/