[TLS] New version intolerance caused by draft-26 supported_versions change?
Joseph Birr-Pixton <jpixton@gmail.com> Mon, 09 April 2018 21:16 UTC
Return-Path: <jpixton@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 8B2D312D944 for <tls@ietfa.amsl.com>; Mon, 9 Apr 2018 14:16:49 -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 dRHNFRnul9ww for <tls@ietfa.amsl.com>; Mon, 9 Apr 2018 14:16:47 -0700 (PDT)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (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 7860C12D7EF for <tls@ietf.org>; Mon, 9 Apr 2018 14:16:47 -0700 (PDT)
Received: by mail-oi0-x231.google.com with SMTP id e123-v6so9077667oih.13 for <tls@ietf.org>; Mon, 09 Apr 2018 14:16:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=FymfYiIIz5iawKv99N5fj2kYt+yJXuDbR4JdJMHZygE=; b=U99FkW+kFoqEjaCNsuWlt1ifjgQTriWaTI4umUnIAhjZ1KKK8JFgXXc6RKKC4vvuCj Xvt3O9ctpYE33RtCZaTV2TJL5tCPynLaqtm4KYMBeik6kDeG+JkTNqYfytId38a+PYHl wSFMmSY7MzKnCB/zXLXko6QT8dpFMlLYUqsUF+SEVyyIYPnU1ycrbruT0tBMk1pcdkr0 GnIolOaGADKlYnbZ1hxH5+KFNdfOgh+pTQz9WlYRdeOIOzsOFSy3z6tLC8leOvd+qTUl KSbvcCyXbeGZ38x538VFGHfN0/0y1qn6viOgpiD4jSm5pHpZI9dFh668Z6nQsllaA6va orqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=FymfYiIIz5iawKv99N5fj2kYt+yJXuDbR4JdJMHZygE=; b=cuizNwQDUq2FsTy1+bKdQKy+zrv5OeQs3T1yvhZe67EwtY3mKj29BOvAbDJMNoINWT cd7wEFHpXs2xjSLDOq19UmLUPpMzEr6RiCm/E/AZmcr7NWYZpnmwJlLmiY2oZ1h70lQ3 UFYXgMPiXxb541FYbNuhINsqKTlsWHcmS0GZu8nRa8vwGpK+6gqG0hZo6qRC3B5mFDrd 061PKbikUWEPaha3w3xvyAv24UnFDMdMyXCn2a7TRLSKF+dZX2YjWzNV74KayD9qpiu2 iB5Vu1I+eOD8vChTaAx7/MHKp6FOpv/B4NGMU48zRlvlzb4p6aCBZosePj0pb3Rls19e ODrA==
X-Gm-Message-State: ALQs6tA8rre0wHwjbHZMqFhdm4mAK82s4KJgdABEedaBQMba7hQiZSr9 aud6B5LhgDYbWmtH2vZh1mr3uvOiJeJuMOH8QqwPDsI/
X-Google-Smtp-Source: AIpwx48DNERg+FJqT/HcDA9bkvQkou9gKN5Ap9a3W62bOmVV0g0dwMkdGVEk282Cs67FZuSNTLsuqhOtVgvxD1YRsmA=
X-Received: by 2002:aca:7258:: with SMTP id p85-v6mr359749oic.349.1523308606579; Mon, 09 Apr 2018 14:16:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.113.145 with HTTP; Mon, 9 Apr 2018 14:16:06 -0700 (PDT)
From: Joseph Birr-Pixton <jpixton@gmail.com>
Date: Mon, 09 Apr 2018 22:16:06 +0100
Message-ID: <CACaGAp=X6Bwa26jx-=kU13TQG4r5PjZ9qyY+4t6gXzcqVfD71Q@mail.gmail.com>
To: tls@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/Jb7h-tbhUQDCav4Qn90r6EnhSdQ>
Subject: [TLS] New version intolerance caused by draft-26 supported_versions change?
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: Mon, 09 Apr 2018 21:16:49 -0000
Hello, PR#1163 in draft-26 seems to have broken interop with previous drafts with a variety of deployed implementations. draft-26 and later clients fail with a protocol_version alert. Affected Internet servers include: cloudflare.com: offers draft-23, intolerant to draft-26 www.apple.com: seemingly unwilling to negotiate any draft, but intolerant anyway(?) www.microsoft.com: same google.com: same https://jbp.io/assets/tls13-logs/cloudflare.broken.txt https://jbp.io/assets/tls13-logs/apple.broken.txt https://jbp.io/assets/tls13-logs/microsoft.broken.txt https://jbp.io/assets/tls13-logs/google.broken.txt In all these cases, offering TLS1.2 in supported_versions (ie, the pre-draft-26 behaviour) works, and TLS1.2 is negotiated: https://jbp.io/assets/tls13-logs/cloudflare.works.txt https://jbp.io/assets/tls13-logs/apple.works.txt https://jbp.io/assets/tls13-logs/microsoft.works.txt https://jbp.io/assets/tls13-logs/google.works.txt Corroboration appreciated. It's totally possible I'm doing something stupid :) Thanks, Joe
- [TLS] New version intolerance caused by draft-26 … Joseph Birr-Pixton
- Re: [TLS] New version intolerance caused by draft… Joseph Birr-Pixton
- Re: [TLS] New version intolerance caused by draft… Benjamin Kaduk
- Re: [TLS] New version intolerance caused by draft… Salz, Rich
- Re: [TLS] New version intolerance caused by draft… Eric Rescorla