Re: [TLS] TLS@IETF101 Agenda Posted

Peter Bowen <pzbowen@gmail.com> Wed, 14 March 2018 19:56 UTC

Return-Path: <pzbowen@gmail.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 E4B9A126B7E for <tls@ietfa.amsl.com>; Wed, 14 Mar 2018 12:56:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 65Sgl1u8lvtm for <tls@ietfa.amsl.com>; Wed, 14 Mar 2018 12:56:01 -0700 (PDT)
Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFB8E1200F1 for <tls@ietf.org>; Wed, 14 Mar 2018 12:56:00 -0700 (PDT)
Received: by mail-lf0-x22f.google.com with SMTP id h127-v6so6624805lfg.12 for <tls@ietf.org>; Wed, 14 Mar 2018 12:56:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RC40cs6K03JV7y3baKgFZyhP7G4/udmOp5ZTGZgTeyI=; b=eg2lMxb7jxEW4TPyPmFSBQnCrCeL19x9JpZMvvS6FR9aAaPM1ZYdCaOCrxX5iNckms LxRlq9lMmqCVu6uvFhj72542P2HnOB85t+nu+0V060uoZHXfVEDp1AQCadHfQGkwItHA 3VWGKc+PAcNeyTkTi8j8+YGxzhvI0qnv8TcG5BagUZ+ytZm/Y7NUBeRpMSG8bWHDgiGh b67FYfNMVrbNCjYf/xGL1bmGagBoRhl58wmfYdgFnOjxZ/QquNhg9ZGI8AvCwgDduYZ2 OnsQdJg6qlY2a7RBUt6YQ015tfKbaRCPsX3hqTm9IehKsCX1/Z55UDC+N5FxSnALfRO/ ZNzQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RC40cs6K03JV7y3baKgFZyhP7G4/udmOp5ZTGZgTeyI=; b=qLQpFZI5kwEsW/BSPNnn2Dpz5wQtpe1KDU/9B8LgKTaeaV24GEbhKu9iEEEcClJzVR 69ZZHeyDoRYo++AiEa0w7Z2nuNL1fwXbYzoW6q9VGe1tK8uL6CjBothywEnP5QIDR1tl bgUFMVL5NcKiv9cVJiw7c88oXtXbhFefVEiMf8BldM7K0fsn9fdO//sDumXPvNROs3+w nTG3Bzu5VEnsTbaZz9/WIMFxQAtsyLpmZcD9cmWFKrEFRCCqLaQZape/tj9zGVk04BJG bg0XGCPT5HMlYE7kLS3edSLic8wgu8aRujLKGn7mBzED+86CtMDIv/C9oU+NyC4soZ0F Kw4Q==
X-Gm-Message-State: AElRT7HhN+orc+/Rgcz1RgL35ypAbOsGDOJMmARlytE15pSYLUWB8Lb8 NEo1xvm0o3sPTg2E1OD9kcmcGWSBKAVaKklJdLh8TLqV
X-Google-Smtp-Source: AG47ELtnRgw44qWoC3sLo/XaTHYNCqLTOcJbXVYec4t6UK6kUob2EfPAHrgg7LmDz82cMehfQl+uVVBAE3KicGD1L0c=
X-Received: by 10.46.86.1 with SMTP id k1mr4125005ljb.28.1521057359006; Wed, 14 Mar 2018 12:55:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:1a4f:0:0:0:0:0 with HTTP; Wed, 14 Mar 2018 12:55:58 -0700 (PDT)
In-Reply-To: <C1970611-C781-41A8-87CA-D00629AC41E7@vigilsec.com>
References: <6140B7A6-A1C7-44BC-9C65-9BE0D5E1B580@sn3rd.com> <986797a7-81b0-7874-5f39-afe83c86635b@cs.tcd.ie> <CAOgPGoBYc7O+qmjM-ptkRkE6mRsOYgc5O7Wu9pm3drFp3TVa6Q@mail.gmail.com> <d7dfdc1a-2c96-fd88-df1b-3167fe0f804b@cs.tcd.ie> <CAHbuEH7E8MhFcMt2GSngSrGxN=6bU6LD49foPC-mdoUZboH_0Q@mail.gmail.com> <1a024320-c674-6f75-ccc4-d27b75e3d017@nomountain.net> <2ed0gc.p5dcxd.31eoyz-qmf@mercury.scss.tcd.ie> <d7ec110f-2a0b-cf97-94a3-eeb5594d8c24@cs.tcd.ie> <CAAF6GDcaG7nousyQ6wotEg4dW8PFuXi=riH2702eZZn2fwfLQw@mail.gmail.com> <CAPsNn2XCNtqZaQM6Bg8uoMZRJE+qQakEwvw8Cn9fBm-5H+Xn_A@mail.gmail.com> <3F8142DE-EADB-4AB9-A204-7D87ACDCD3E3@akamai.com> <CAPsNn2VE_7+rWT0fp9rrVnZrgcY7ORLWTee+kf_Av1dqm4CiDQ@mail.gmail.com> <CB55AABB-8937-4F6B-B5AC-B6F262F08A4F@akamai.com> <CAPsNn2U_xG28Tumo3oRkQ+6=BHzgv-6YtgNSpwvhdFFRWc7EQQ@mail.gmail.com> <2DC45296-244E-4C72-8B3C-DE47EADAC2DE@fugue.com> <BN7PR14MB23696A2767FF9C1A410110AFD7D20@BN7PR14MB2369.namprd14.prod.outlook.com> <090F06AF-371D-4B11-91AA-BD80C1ADB4E9@fugue.com> <C1970611-C781-41A8-87CA-D00629AC41E7@vigilsec.com>
From: Peter Bowen <pzbowen@gmail.com>
Date: Wed, 14 Mar 2018 12:55:58 -0700
Message-ID: <CAK6vND9-1v3VBgFm6UX-tXPCFBWKTQHXHC_ZADVpeQ_1WRsk2A@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>
Cc: Ted Lemon <mellon@fugue.com>, IETF TLS <tls@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/VFEC9yTvKVhixFLpxyr0V9YOHHw>
Subject: Re: [TLS] TLS@IETF101 Agenda Posted
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 14 Mar 2018 19:56:03 -0000

On Tue, Mar 13, 2018 at 3:16 PM, Russ Housley <housley@vigilsec.com> wrote:
> Second, using
> TLS1.2 does not technically address the issue.  If the client were to
> exclusively offer DHE-based ciphersuites, then the visibility techniques
> that have been used in the past are thwarted.

I expect this configuration to become more common in the future.  In
November 2017, US NIST published draft SP 800-52 r2
(https://csrc.nist.gov/publications/detail/sp/800-52/rev-2/draft )
which explicitly disallows all non-DH cipher suites.  The comment
period closed on 1 Feb 2018, and none of the published comments pushed
back on this.  Given that PCI DSS and many other standards refer to
the NIST Special Publications for implementation requirements, I would
not be surprised to see DH-only (including ECDH/ECDHE/DHE) become
prevalent.

Based on the comments from the proponents of the various drafts, it
would seem that this should be a bigger concern than any changes in
TLS 1.3, as it is implementable today.  I highly suspect that the
currently deployed systems will not handle handshakes that only offer
DH suites, right?

Thanks,
Peter