draft-ietf-curdle-rc4-die-die-die-12.txt		draft-ietf-curdle-rc4-die-die-die-13.txt
	Internet Engineering Task Force L. Camara		Internet Engineering Task Force L. Camara
	Internet-Draft		Internet-Draft
	Obsoletes: 4345 (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 18, 2019 October 15, 2018		Expires: May 24, 2019 November 20, 2018
	Deprecating RC4 in Secure Shell (SSH)		Deprecating RC4 in Secure Shell (SSH)
	draft-ietf-curdle-rc4-die-die-die-12		draft-ietf-curdle-rc4-die-die-die-13
	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.
	skipping to change at page 1, line 32 ¶		skipping to change at page 1, line 32 ¶
	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 18, 2019.		This Internet-Draft will expire on May 24, 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 24 ¶		skipping to change at page 2, line 24 ¶
	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 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 has known weaknesses [RFC7465]
	[RFC7465] [I-D.ietf-curdle-des-des-des-die-die-die], and the		[I-D.ietf-curdle-des-des-des-die-die-die], and the deprecation
	deprecation process should be begun for their use in Secure Shell		process should be begun for their use in Secure Shell (SSH)
	(SSH) [RFC4253]. Accordingly, [RFC4253] is updated to note the		[RFC4253]. Accordingly, [RFC4253] is updated to note the deprecation
	deprecation of the RC4 ciphers and [RFC4345] is moved to Historic as		of the RC4 ciphers and [RFC4345] is moved to Historic as all ciphers
	all ciphers it specifies MUST NOT be used.		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
	document are to be interpreted as described in RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	2. Updates to RFC 4253		2. Updates to RFC 4253
	[RFC4253] is updated to prohibit arcfour's use in SSH. [RFC4253]		[RFC4253] is updated to prohibit arcfour's use in SSH. [RFC4253]
	skipping to change at page 3, line 23 ¶		skipping to change at page 3, line 23 ¶
	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 believed to be compatible with the RC4 cipher		The Arcfour cipher is believed to be compatible with the RC4 cipher
	[SCHNEIER]. Arcfour (and RC4) has problems with weak keys, and		[SCHNEIER]. Arcfour (and RC4) has problems with weak keys, and
	should be used with caution.		should be used with caution.
	The current document updates [RFC4253] Section 6.3 by replacing the		The 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 believed to be compatible with the RC4 cipher		The Arcfour cipher is believed to be compatible with the RC4 cipher
	[SCHNEIER]. Arcfour (and RC4) is steadily weakening in cryptographic		[SCHNEIER]. Arcfour (and RC4) has known weakenesses [RFC7465]
	strength [RFC7465] [I-D.ietf-curdle-des-des-des-die-die-die], and		[I-D.ietf-curdle-des-des-des-die-die-die], and MUST NOT be used.
	MUST 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:
	+-------------+------------------------------------+		+-------------+------------------------------------+
	| 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.
	4. Acknowledgements		4. Acknowledgements
	The authors would like to thank Daniel Migault and Rich Salz.		The authors would like to thank Eric Rescorla, 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
End of changes. 6 change blocks.
	13 lines changed or deleted		13 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/