< draft-ietf-tls-md5-sha1-deprecate-05.txt   draft-ietf-tls-md5-sha1-deprecate-06.txt >
Internet Engineering Task Force L. Velvindron Internet Engineering Task Force L. Velvindron
Internet-Draft cyberstorm.mu Internet-Draft cyberstorm.mu
Updates: 5246 7525 (if approved) K. Moriarty Updates: 5246 7525 (if approved) K. Moriarty
Intended status: Standards Track Dell Technologies Intended status: Standards Track Dell Technologies
Expires: September 24, 2021 A. Ghedini Expires: September 30, 2021 A. Ghedini
Cloudflare Inc. Cloudflare Inc.
March 23, 2021 March 29, 2021
Deprecating MD5 and SHA-1 signature hashes in TLS 1.2 Deprecating MD5 and SHA-1 signature hashes in TLS 1.2
draft-ietf-tls-md5-sha1-deprecate-05 draft-ietf-tls-md5-sha1-deprecate-06
Abstract Abstract
The MD5 and SHA-1 hashing algorithms are increasingly vulnerable to The MD5 and SHA-1 hashing algorithms are increasingly vulnerable to
attack and this document deprecates their use in TLS 1.2 digital attack and this document deprecates their use in TLS 1.2 digital
signatures. However, this document does not deprecate SHA-1 in HMAC signatures. However, this document does not deprecate SHA-1 in HMAC
for record protection. This document updates RFC 5246 and RFC 7525. for record protection. This document updates RFC 5246 and RFC 7525.
Status of This Memo Status of This Memo
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 September 24, 2021. This Internet-Draft will expire on September 30, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the Copyright (c) 2021 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 4, line 20 skipping to change at page 4, line 20
recommendation to use stronger language deprecating use of both SHA-1 recommendation to use stronger language deprecating use of both SHA-1
and MD5. The prior text did not explicitly include MD5 or SHA-1; and and MD5. The prior text did not explicitly include MD5 or SHA-1; and
this text adds guidance to ensure that these algorithms have been this text adds guidance to ensure that these algorithms have been
deprecated. deprecated.
Section 4.3: Section 4.3:
OLD: OLD:
When using RSA, servers SHOULD authenticate using certificates with When using RSA, servers SHOULD authenticate using certificates with
at least a 2048-bit modulus for the public key. In addition, the use at least a 2048-bit modulus for the public key. In addition, SHA-256
of the SHA-256 hash algorithm is RECOMMENDED (see [CAB-Baseline] for hash algorithm MUST be used (see [CAB-Baseline] for more details).
more details). Clients SHOULD indicate to servers that they request Clients SHOULD indicate to servers that they request SHA-256, by
SHA-256, by using the "Signature Algorithms" extension defined in TLS using the "Signature Algorithms" extension defined in TLS 1.2.
1.2.
NEW: NEW:
Servers SHOULD authenticate using certificates with at least a Servers SHOULD authenticate using certificates with at least a
2048-bit modulus for the public key. 2048-bit modulus for the public key.
In addition, the use of the SHA-256 hash algorithm is RECOMMENDED; In addition, the SHA-256 hash algorithm MUST be used; and SHA-1 or
and SHA-1 or MD5 MUST NOT be used (see [CAB-Baseline] for more MD5 MUST NOT be used (see [CAB-Baseline] for more details). Clients
details). Clients MUST indicate to servers that they request SHA- MUST indicate to servers that they request SHA-256, by using the
256, by using the "Signature Algorithms" extension defined in TLS "Signature Algorithms" extension defined in TLS 1.2.
1.2.
8. IANA Considerations 8. IANA Considerations
The document updates the "TLS SignatureScheme" registry to change the The document updates the "TLS SignatureScheme" registry to change the
recommended status of SHA-1 based signature schemes to N (not recommended status of SHA-1 based signature schemes to N (not
recommended) as defined by [RFC8447]. The following entries are to recommended) as defined by [RFC8447]. The following entries are to
be updated: be updated:
+--------+----------------+-------------+--------------------+ +--------+----------------+-------------+--------------------+
| Value | Description | Recommended | Reference | | Value | Description | Recommended | Reference |
 End of changes. 6 change blocks. 
14 lines changed or deleted 12 lines changed or added

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