| RFC 8758 | Deprecating RC4 in SSH | April 2020 |
| Velvindron | Best Current Practice | [Page] |
This document deprecates RC4 in Secure Shell (SSH). Therefore, this document formally moves RFC 4345 to Historic status.¶
This memo documents an Internet Best Current Practice.¶
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 7841.¶
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained athttps://www.rfc-editor.org/info/rfc8758.¶
Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶
The usage of RC4 suites (also designated as "arcfour") for SSH is specified in[RFC4253] and[RFC4345].[RFC4253] specifies the allocation of the "arcfour" cipher for SSH.[RFC4345] specifies and allocates the "arcfour128" and "arcfour256" ciphers for SSH. RC4 encryption has known weaknesses[RFC7465][RFC8429]; therefore, this document starts the deprecation process for their use in Secure Shell (SSH)[RFC4253]. Accordingly,[RFC4253] is updated to note the deprecation of the RC4 ciphers, and[RFC4345] is moved to Historic status, as all ciphers it specifiesMUST NOT be used.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14[RFC2119][RFC8174] when, and only when, they appear in all capitals, as shown here.¶
[RFC4253] is updated to prohibit arcfour's use in SSH.[RFC4253],Section 6.3 allocates the"arcfour" cipher by defining a list of defined ciphers in which the "arcfour"cipher appears as optional, as shown inTable 1.¶
| arcfour | OPTIONAL | the ARCFOUR stream cipher with a 128-bit key |
This document updates the status of the "arcfour" ciphers in the listfound in[RFC4253],Section 6.3 by moving itfromOPTIONAL toMUST NOT.¶
| arcfour | MUST NOT | the ARCFOUR stream cipher with a 128-bit key |
[RFC4253] defines the "arcfour" ciphers withthe following text:¶
The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys. The Arcfour cipher is believed to be compatible with the RC4 cipher[SCHNEIER]. Arcfour (and RC4) has problems with weak keys, and should be used with caution.¶
This document updates[RFC4253],Section 6.3 by replacing the text above with the following text:¶
The "arcfour" cipher is the Arcfour stream cipher with 128-bit keys. The Arcfour cipher is compatible with the RC4 cipher[SCHNEIER]. Arcfour (and RC4) has known weaknesses[RFC7465][RFC8429] andMUST NOT be used.¶
The IANA has updated the "Encryption Algorithm Names" subregistry in the "Secure Shell (SSH) Protocol Parameters" registry[IANA]. The registration procedure is IETF review, which is achieved by this document. The registry has been updated as follows:¶
| Encryption Algorithm Name | Reference | Note |
|---|---|---|
| arcfour | RFC 8758 | HISTORIC |
| arcfour128 | RFC 8758 | HISTORIC |
| arcfour256 | RFC 8758 | HISTORIC |
This document only prohibits the use of RC4 in SSH; it introduces no new security considerations.¶
The author would like to thankEric Rescorla,Daniel Migault, andRich Salz.¶