| Internet-Draft | KEX Method Updates/Recommendations for S | November 2020 |
| Baushke | Expires 27 May 2021 | [Page] |
This document is intended to update the recommended set of key exchange methods for use in the Secure Shell (SSH) protocol to meet evolving needs for stronger security. This document updates RFC 4250.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 27 May 2021.¶
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.¶
Secure Shell (SSH) is a common protocol for secure communication on the Internet. In [RFC4253], SSH originally defined two Key Exchange (KEX) Method Names that MUST be implemented. Over time what was once considered secure is no longer considered secure. The purpose of this RFC is to recommend that some published key exchanges be deprecated as well as recommending some that SHOULD and one that MUST be adopted. This document updates [RFC4250].¶
A key exchange has two components, a hashing algorithm and a public key algorithm. The following subsections describe how to select each component.¶
The SHA-1 hash is in the process of being deprecated for many reasons. There have been attacks against SHA-1 that have shown there are weaknesses in the algorithm. Therefore, it is desirable to move away from using it before attacks become more serious.¶
At present, the attacks against SHA-1 are collision attacks that rely on human help rather than a pre-image attack. So, it is still possible to allow time backward compatibility use of SHA-1 during a SSH key-exchange for a transition to stronger hashing. However, any such key exchanges should be listed last in the preference list.¶
Use of the SHA-2 family of hashes found in [RFC6234] rather than the SHA-1 hash is strongly advised.¶
When it comes to the SHA-2 family of Secure Hashing functions, SHA2-224 has 112 bits of security strength; SHA2-256 has 128 bits of security strength; SHA2-384 has 192 bits of security strength; and SHA2-512 has 256 bits of security strength. As the same compute power is needed for both SHA2-224 and SHA2-256 and currently no KeX uses SHA2-224, it is suggested that the minimum secure hashing function that should be used for Key Exchange Methods is SHA2-256.¶
To avoid combinatorial explosion of key exchange names, newer key exchanges are restricting to the use of *-sha256 and *-sha512.¶
SSH uses mathematically hard problems for doing Key Exchange:¶
It is desirable for the security strength of the key exchange be chosen to be comparable with the security strength of the other elements of the SSH handshake. Attackers can target the weakest element of the SSH handshake.¶
It is desirable to select a minimum of 112 bits of security strength. Based on implementer security needs, a stronger minimum may be desired.¶
For ECC, it is recommended to select one with approximately 128 bits of security strength.¶
| Curve Name | Estimated Security Strength |
|---|---|
| nistp256 | 128 bits |
| nistp384 | 192 bits |
| nistp521 | 512 bits |
| Curve25519 | 128 bits |
| Curve448 | 224 bits |
For FFC, a modulus 2048 bits (112 bits of security strength).¶
| Prime Field Size | Estimated Security Strength | Example MODP Group |
|---|---|---|
| 2048-bit | 112 bits | group14 |
| 3072-bit | 128 bits | group15 |
| 4096-bit | 152 bits | group16 |
| 6144-bit | 176 bits | group17 |
| 8192-bit | 200 bits | group18 |
The minimum MODP group that MAY be used is the 2048-bit MODP group14. Implementations SHOULD support a 3072-bit MODP group or larger.¶
The only IFC algorithm for key exchange is the RSA algorithm via [RFC4432]. The minimum modulus size is 2048 bits. The use of a SHA-2 Family hash with RSA 2048-bit keys has sufficient security.¶
| Key Exchange Method | Estimated Security Strength |
|---|---|
| rsa1024-sha1 | 80 bits |
| rsa2048-sha256 | 112 bits |
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.¶
This memo adopts the style and conventions of [RFC4253] in specifying how the use of data key exchange is indicated in SSH.¶
This RFC also collects key exchange method names in various existing RFCs [RFC4253], [RFC4419], [RFC4432], [RFC4462], [RFC5656], [RFC8268], [RFC8731], [RFC8732], and [RFC8308], and provides a suggested suitability for implementation of MUST, SHOULD, SHOULD NOT, and MUST NOT. Any method not explicitly listed MAY be implemented.¶
This document is intended to provide guidance as to what key exchange algorithms are to be considered for new or updated SSH implementations.¶
All of the key exchanges using the SHA-1 hashing algorithm should be deprecated and phased out of use because SHA-1 has security concerns provided in [RFC6194]. The SHA-2 Family of hashes [RFC6234] is the only one which is more secure than SHA-1 and has been standardized for use with SSH key exchanges.¶
diffie-hellman-group1-sha1 and diffie-hellman-group14-sha1 are currently mandatory to implement (MTI). diffie-hellman-group14-sha1 is the stronger of the two. Group14 (a 2048-bit MODP group) is defined in [RFC3526]. It is reasonable to retain the diffie-hellman-group14-sha1 exchange for interoperability with legacy implementations. Therefore, diffie-hellman-group14-sha1 SHOULD be implemented and all other *-sha1 key exchanges SHOULD NOT be implemented.¶
Curve25519 is efficient on a wide range of architectures with properties that allow higher performance implementations compared to traditional elliptic curves. The use of SHA2-256 (also known as SHA-256 and sha256) as defined in [RFC6234] for integrity is a reasonable one for this method. These key exchange methods are described in [RFC8731] and [RFC8732] and is similar to the IKEv2 Key Agreement described in [RFC8031]. The curve25519-sha256 key exchange method has multiple implementations and SHOULD be implemented. The gss-curve25519-sha256-* key exchange method SHOULD also be implemented because it shares the same performance and security characteristics as curve25519-sha2.¶
Curve448 provides more security strength than Curve25519 at a higher computational and bandwidth cost. It uses SHA2-512 (also known as SHA-512) defined in [RFC6234] for integrity. This Key Exchange Method is described in [RFC8731] and is similar to the IKEv2 Key Agreement described in [RFC8031]. This method MAY be implemented. The gss-curve448-sha512-* key exchange method MAY also be implemented because it shares the same performance and security characteristics as curve448-sha512.¶
The ecdh-sha2-* name-space allows for other curves to be defined for the elliptic curve Diffie Hellman key exchange. At present, there are three named curves in this name-space which SHOULD be supported. They appear in [RFC5656] in section 10.1 Required Curves all of the NISTP curves named are mandatory to implement if any of this RFC is implemented. This set of methods MAY be implemented. If implemented, the named curves SHOULD always be enabled unless specifically disabled by local security policy. In [RFC5656], section 6.1, the method to name other ECDH curves using OIDs is specified. These other curves MAY be implemented.¶
The GSS-API name-space with gss-nistp*-sha* mirrors the algorithms used by ecdh-sha2-* names. The table provides guidance for implementation.¶
ECDH reduces bandwidth of key exchanges compared to FFC DH at a similar security strength.¶
The following table lists algorithms as SHOULD where implementations may be more efficient or widely deployed. The items listed as MAY are potentially less efficient.¶
| Key Exchange Method Name | Guidance |
|---|---|
| ecdh-sha2-* | MAY |
| ecdh-sha2-nistp256 | SHOULD |
| gss-nistp256-sha256-* | SHOULD |
| ecdh-sha2-nistp384 | SHOULD |
| gss-nistp384-sha384-* | SHOULD |
| ecdh-sha2-nistp521 | SHOULD |
| gss-nistp521-sha512-* | SHOULD |
| ecmqv-sha2 | MAY |
It is advisable to match the ECDSA and ECDH algorithms to use the same curve for both to maintain the same security strength in the connection.¶
This random selection from a set of pre-generated moduli for key exchange uses SHA2-256 as defined in [RFC4419]. [RFC8270] mandates implementations avoid any MODP group whose modulus size is less than 2048 bits. Care should be taken in the pre-generation of the moduli P and generator G such that the generator provides a Q-ordered subgroup of P. Otherwise, the parameter set may leak one bit of the shared secret leaving the MODP group half as strong. This key exchange MAY be used.¶
diffie-hellman-group14-sha256 represents the smallest FFC DH key exchange method considered to be secure. It is a reasonably simple transition from SHA-1 to SHA-2. diffie-hellman-group14-sha256 method MUST be implemented. The rest of the FFC MODP groups MAY be implemented. The table below provides explicit guidance by name.¶
| Key Exchange Method Name | Guidance |
|---|---|
| diffie-hellman-group14-sha256 | MUST |
| gss-group14-sha256-* | SHOULD |
| diffie-hellman-group15-sha512 | MAY |
| gss-group15-sha512-* | MAY |
| diffie-hellman-group16-sha512 | SHOULD |
| gss-group16-sha512-* | MAY |
| diffie-hellman-group17-sha512 | MAY |
| gss-group17-sha512-* | MAY |
| diffie-hellman-group18-sha512 | MAY |
| gss-group18-sha512-* | MAY |
The rsa2048-sha256 key exchange method is defined in [RFC4432]. Uses an RSA 2048-bit modulus with a SHA2-256 hash. This key exchange meets 112 bit minimum security strength. This method MAY be implemented.¶
There are two key exchange methods, ext-info-c and ext-info-s, defined in [RFC8308] which are not actually key exchanges. They provide a method to support other Secure Shell negotiations. Being able to extend functionality is desirable. This method SHOULD be implemented.¶
The Implement column is the current recommendations of this RFC. Key Exchange Method Names are listed alphabetically.¶
| Key Exchange Method Name | Reference | Implement |
|---|---|---|
| curve25519-sha256 | RFC8731 | SHOULD |
| curve448-sha512 | RFC8731 | MAY |
| diffie-hellman-group-exchange-sha1 | RFC4419 | SHOULD NOT |
| diffie-hellman-group-exchange-sha256 | RFC4419 | MAY |
| diffie-hellman-group1-sha1 | RFC4253 | SHOULD NOT |
| diffie-hellman-group14-sha1 | RFC4253 | SHOULD |
| diffie-hellman-group14-sha256 | RFC8268 | MUST |
| diffie-hellman-group15-sha512 | RFC8268 | MAY |
| diffie-hellman-group16-sha512 | RFC8268 | SHOULD |
| diffie-hellman-group17-sha512 | RFC8268 | MAY |
| diffie-hellman-group18-sha512 | RFC8268 | MAY |
| ecdh-sha2-* | RFC5656 | MAY |
| ecdh-sha2-nistp256 | RFC5656 | SHOULD |
| ecdh-sha2-nistp384 | RFC5656 | SHOULD |
| ecdh-sha2-nistp521 | RFC5656 | SHOULD |
| ecmqv-sha2 | RFC5656 | MAY |
| ext-info-c | RFC8308 | SHOULD |
| ext-info-s | RFC8308 | SHOULD |
| gss-* | RFC4462 | MAY |
| gss-curve25519-sha256-* | RFC8732 | SHOULD |
| gss-curve448-sha512-* | RFC8732 | MAY |
| gss-gex-sha1-* | RFC4462 | SHOULD NOT |
| gss-group1-sha1-* | RFC4462 | SHOULD NOT |
| gss-group14-sha256-* | RFC8732 | SHOULD |
| gss-group15-sha512-* | RFC8732 | MAY |
| gss-group16-sha512-* | RFC8732 | SHOULD |
| gss-group17-sha512-* | RFC8732 | MAY |
| gss-group18-sha512-* | RFC8732 | MAY |
| gss-nistp256-sha256-* | RFC8732 | SHOULD |
| gss-nistp384-sha384-* | RFC8732 | SHOULD |
| gss-nistp521-sha512-* | RFC8732 | MAY |
| rsa1024-sha1 | RFC4432 | MUST NOT |
| rsa2048-sha256 | RFC4432 | MAY |
The full set of official [IANA-KEX] key algorithm method names not otherwise mentioned in this document MAY be implemented.¶
[TO BE REMOVED: This registration should take place at the following location URL: http://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml#ssh-parameters-16 ]¶
Thanks to the following people for review and comments: Denis Bider, Peter Gutmann, Damien Miller, Niels Moeller, Matt Johnston, Iwamoto Kouichi, Simon Josefsson, Dave Dugal, Daniel Migault, Anna Johnston, Tero Kivinen, and Travis Finkenauer.¶
Thanks to the following people for code to implement interoperable exchanges using some of these groups as found in an this draft: Darren Tucker for OpenSSH and Matt Johnston for Dropbear. And thanks to Iwamoto Kouichi for information about RLogin, Tera Term (ttssh) and Poderosa implementations also adopting new Diffie-Hellman groups based on this draft.¶
This SSH protocol provides a secure encrypted channel over an insecure network. It performs server host authentication, key exchange, encryption, and integrity checks. It also derives a unique session ID that may be used by higher-level protocols.¶
Full security considerations for this protocol are provided in [RFC4251].¶
It is desirable to deprecate or remove key exchange method name that are considered weak. A key exchange method may be weak because too few bits are used, or the hashing algorithm is considered too weak.¶
IANA is requested to annotate entries in [IANA-KEX] which MUST NOT be implemented as being deprecated by this document.¶