Re: [TLS] Working Group Last Call for draft-ietf-tls-downgrade-scsv-00

Florian Weimer <fw@deneb.enyo.de> Wed, 29 October 2014 11:27 UTC

Return-Path: <fw@deneb.enyo.de>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BAC71A000C for <tls@ietfa.amsl.com>; Wed, 29 Oct 2014 04:27:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.339
X-Spam-Level:
X-Spam-Status: No, score=0.339 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_DE=0.35, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 gBZtUX7N10W3 for <tls@ietfa.amsl.com>; Wed, 29 Oct 2014 04:27:02 -0700 (PDT)
Received: from albireo.enyo.de (albireo.enyo.de [46.237.207.196]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F74E1A000B for <tls@ietf.org>; Wed, 29 Oct 2014 04:27:02 -0700 (PDT)
Received: from [172.17.203.2] (helo=deneb.enyo.de) by albireo.enyo.de with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) id 1XjRP2-0005pS-Ex for tls@ietf.org; Wed, 29 Oct 2014 12:27:00 +0100
Received: from fw by deneb.enyo.de with local (Exim 4.80) (envelope-from <fw@deneb.enyo.de>) id 1XjRP2-0000hC-84 for tls@ietf.org; Wed, 29 Oct 2014 12:27:00 +0100
From: Florian Weimer <fw@deneb.enyo.de>
To: "tls@ietf.org" <tls@ietf.org>
References: <544E9A42.9080503@fifthhorseman.net> <20141029023528.B14E71AF5F@ld9781.wdf.sap.corp> <CADMpkcLLOrUQMxbeCW7RB+Gf12Ux_wK_eotKdbH0RMpeuaptfQ@mail.gmail.com>
Date: Wed, 29 Oct 2014 12:27:00 +0100
In-Reply-To: <CADMpkcLLOrUQMxbeCW7RB+Gf12Ux_wK_eotKdbH0RMpeuaptfQ@mail.gmail.com> (Bodo Moeller's message of "Wed, 29 Oct 2014 10:55:58 +0100")
Message-ID: <87oasvp14r.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/NOrjLgPkz0mQrxkgaw8AacwBtiM
Subject: Re: [TLS] Working Group Last Call for draft-ietf-tls-downgrade-scsv-00
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 29 Oct 2014 11:27:03 -0000

* Bodo Moeller:

> I think you have mentioned that issue before, but I must admit that I am
> not sure I understand what your concern is. If you are referring to
> https://bugzilla.mozilla.org/show_bug.cgi?id=1072382, that's a bug that was
> found and fixed *because* TLS_FALLBACK_SCSV was rolled out. How, then, is
> this an argument *against* TLS_FALLBACK_SCSV semantics?

This bug in the fallback logic was actually reported in 2008:

  <https://bugzilla.mozilla.org/show_bug.cgi?id=450280>

My concern is that this bug has tainted the telemetry data collected
by Mozilla, and may have grossly exaggerated the need for fallback.
And as far as I can tell, the patch for bug 1072382 only makes the
fallback less sticky, it still does not result in better reporting of
fallbacks in telemetry data.