Re: [TLS] 3GPP forbids support of MD5, SHA-1, non-AEAD, and non-PFS in TLS
John Levine <johnl@taugh.com> Sun, 08 March 2020 16:29 UTC
Return-Path: <johnl@iecc.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF7CF3A0CD7 for <tls@ietfa.amsl.com>; Sun, 8 Mar 2020 09:29:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=Go7noWVj; dkim=pass (1536-bit key) header.d=taugh.com header.b=UNA4wCCu
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aK9BdGowFe2a for <tls@ietfa.amsl.com>; Sun, 8 Mar 2020 09:29:47 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F0BE3A0CD6 for <tls@ietf.org>; Sun, 8 Mar 2020 09:29:46 -0700 (PDT)
Received: (qmail 64826 invoked from network); 8 Mar 2020 16:29:44 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding;s=fd38.5e651d78.k2003; bh=ePTltj2Fuqk0ej4Ycf0scKgdaEVu0vSBo9DpQ78vqwg=; b=Go7noWVj+4Jkoq+e2V5o2Q1Z9LzUj6Qen0ie/dn9xyX0qtyyR8sUVSSIbi5zLxm3q6XEyx0zXHmNeM0THzcRRdNMeDrJdGVa9w8UMIVRqlM+ABvB1Qq48hA8653eRkyeOXx+9g4jFKzttRvkqszhj80A3sbpJ5j4EdjyhCV7l5RNHgUCrUD1sENypa7/OUddtXDacf+a1v8xF959mX+Gx9xrgqrGdfcMRFULHLP70x5ldxBnL4bgcd0vXUPnpsjk
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding;s=fd38.5e651d78.k2003; bh=ePTltj2Fuqk0ej4Ycf0scKgdaEVu0vSBo9DpQ78vqwg=; b=UNA4wCCuSFKwCRMwqCkVWlcLybigGZZ1223c+PVfPGlQ243DcydlVnldq1Rp1fgs8ZZvp1+9ZQKH/eLPq1DOaiK4KBJ0VX/5timtTR75qickI/Jtnxe5ai1Q4qcwhqHhViKzdwV6E+Qs1s7AelPO7wtFv7GcV5WegaKqWihK9nJnQe/Sw4WIA03BnetfagqiKJZmG0NeZtif8cVqIAMhf+5skwY4BlFrGJGJyMR5jYtjQI5ZzRWNco4CgS78xaqg
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 08 Mar 2020 16:29:43 -0000
Received: by ary.qy (Postfix, from userid 501) id E5FE41599969; Sun, 8 Mar 2020 12:29:43 -0400 (EDT)
Date: Sun, 08 Mar 2020 12:29:43 -0400
Message-Id: <20200308162943.E5FE41599969@ary.qy>
From: John Levine <johnl@taugh.com>
To: tls@ietf.org
In-Reply-To: <9af29b8f-856e-eb3f-6f12-e4cb0a86677b@cs.tcd.ie>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/mZSX21SQFvRSAj2iJbbJJ0NrW9M>
Subject: Re: [TLS] 3GPP forbids support of MD5, SHA-1, non-AEAD, and non-PFS in TLS
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Mar 2020 16:29:49 -0000
In article <9af29b8f-856e-eb3f-6f12-e4cb0a86677b@cs.tcd.ie> you write: >On 08/03/2020 14:46, Tony Rutkowski wrote: >> >> TLS is particular has a history going back to 1986 when the platform was >> first announced by the USG and the TLS specification was instantiated >> initially in the GOSIP standards and then in ITU/ISO standards. > >That's false. I've seen it repeated a few times but it >remains false. Mostly, this falsehood seems to be repeated >in tandem with efforts one could interpret as attempts >to create FUD about Internet related security. ... If anyone wants to confirm that this is FUD, you can find the case documents here: https://www.courtlistener.com/docket/4369665/trueposition-inc-v-lm-ericsson-telephone-company/ R's, John
- [TLS] 3GPP forbids support of MD5, SHA-1, non-AEA… John Mattsson
- Re: [TLS] 3GPP forbids support of MD5, SHA-1, non… Eric Rescorla
- Re: [TLS] 3GPP forbids support of MD5, SHA-1, non… Tony Rutkowski
- Re: [TLS] 3GPP forbids support of MD5, SHA-1, non… Tony Rutkowski
- Re: [TLS] 3GPP forbids support of MD5, SHA-1, non… John Levine
- Re: [TLS] 3GPP forbids support of MD5, SHA-1, non… Tony Rutkowski
- Re: [TLS] 3GPP forbids support of MD5, SHA-1, non… Stephen Farrell
- Re: [TLS] 3GPP forbids support of MD5, SHA-1, non… John Levine
- Re: [TLS] 3GPP forbids support of MD5, SHA-1, non… Tony Rutkowski
- Re: [TLS] 3GPP forbids support of MD5, SHA-1, non… Stephen Farrell
- Re: [TLS] 3GPP forbids support of MD5, SHA-1, non… Tony Rutkowski
- Re: [TLS] 3GPP forbids support of MD5, SHA-1, non… Joseph Salowey