[secdir] Secdir last call review of draft-ietf-tls-md5-sha1-deprecate-04

Rich Salz via Datatracker <noreply@ietf.org> Thu, 22 October 2020 19:22 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Rich Salz via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: tls@ietf.org, last-call@ietf.org, draft-ietf-tls-md5-sha1-deprecate.all@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160339454955.8181.12347313700812158110@ietfa.amsl.com>
Reply-To: Rich Salz <rsalz@akamai.com>
Date: Thu, 22 Oct 2020 12:22:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/W9YTl-krOsdnBLwTlVLAlEA7m5U>
Subject: [secdir] Secdir last call review of draft-ietf-tls-md5-sha1-deprecate-04

Reviewer: Rich Salz
Review result: Has Nits

I'm the assigned security directorate reviewer for this draft. This is intended
for use by the Sec ADs, but anyone else who gleans wisdom from this message is
free to use it as they see fit.

The document is READY.  There are some nits, which can be found at
https://www6.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/draft-ietf-tls-md5-sha1-deprecate-04.txt
or by clicking on the "nits" tab on the datatracker page.

Don't use MD5 or SHA1 as digests.  If you do, bad people in shadows wearing
hoodies will be able to steal your information, impersonate or break your TLS
or other connections, and so on. This document gives more rationale and updates
some RFC's.

This NITS should be fixed, but this should be published.

[secdir] Secdir last call review of draft-ietf-tl… Rich Salz via Datatracker
Re: [secdir] Secdir last call review of draft-iet… Sean Turner