IETF Logo Mail Archive

Re: [TLS] The risk of misconfiguration

Martin Thomson <martin.thomson@gmail.com> Thu, 08 May 2014 16:31 UTC

Return-Path: <martin.thomson@gmail.com>
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 1D1E81A006C for <tls@ietfa.amsl.com>; Thu, 8 May 2014 09:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 QjSkkDB23NWG for <tls@ietfa.amsl.com>; Thu, 8 May 2014 09:31:49 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 3D9F71A006B for <tls@ietf.org>; Thu, 8 May 2014 09:31:49 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id hi2so6991711wib.11 for <tls@ietf.org>; Thu, 08 May 2014 09:31:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6I2ryVqWBrd1PX/PcaVfCntXAzDkKB/itUSDNb14xFw=; b=Kg6Yn8yDabsGQ/YuS3Qs6Eeltgik86482o7AyCqZfO/ZqgosLm5ctvGb3bbVXLog5X Ah13nv+jIxS6sSdzj1ydqc8wOAS5M99PLJpiEiJt1BXANfDxG7BLAzh3soLE3y57QyVY sWdqrcHp7UsMSO7J8vOyf0GthxGwKWJSWPbguSSNSROTYQ1yFJzkr6gajIu31WRhp8XA Kz9eGCW30oKdCFzcXLeJAySXPX1ChySwgzkXC9juxnWimKDnY2BzgFkLPgy/pcVTDJsW /lkNkI013H9ZUj1ayp51Hdox4pw9H9lqimT6rzcaEg1fFJ8LH2lU+bn78HBPZUN2gnSI huLA==
MIME-Version: 1.0
X-Received: by 10.195.18.8 with SMTP id gi8mr2774184wjd.75.1399566704063; Thu, 08 May 2014 09:31:44 -0700 (PDT)
Received: by 10.194.235.163 with HTTP; Thu, 8 May 2014 09:31:43 -0700 (PDT)
In-Reply-To: <2A0EFB9C05D0164E98F19BB0AF3708C7130A13E5A5@USMBX1.msg.corp.akamai.com>
References: <2A0EFB9C05D0164E98F19BB0AF3708C7130A13E3A2@USMBX1.msg.corp.akamai.com> <536A8804.8000207@akr.io> <CAK3OfOgVAg8MLSmRVLe-6vVVzX361xYo4uma3-GQQmn=qoWWbQ@mail.gmail.com> <CACsn0ckrnbQbz-KCEY6u-WU7ULPTQv46g3noz44jMjW5HmFU0g@mail.gmail.com> <CAK3OfOiSKkeknHMwS-a90rR4hF9J9HaNn_XL_b75Mrx3o_wVMQ@mail.gmail.com> <CACsn0cksBt3Mj587cG-U5O5=Kc2p5T1NCP_-LrMRBv1V2hR2wQ@mail.gmail.com> <CAK3OfOibPMSriPsgO286PEZ=N+sdnuDpPyJ_xDr9KdATA_QjLQ@mail.gmail.com> <CACsn0cmB3TQVzsCthYCuY1q-z10wPbmat32Ys9ABT361fYNZLQ@mail.gmail.com> <CAK3OfOgan_JvsuwGNgpzk4tUfoo+JhxbNaHkbZCtAs7DHufr-w@mail.gmail.com> <CACsn0cmeq66S8LS38FmooWpOf534Gda5t09Ro1F3anLb-fJMMQ@mail.gmail.com> <20140508001532.GG27883@mournblade.imrryr.org> <CACsn0ck4mq3LnUwmBwBTgtuA+tHW9_FLHi1zdkz-ApkmtZs7eg@mail.gmail.com> <2A0EFB9C05D0164E98F19BB0AF3708C7130A13E47E@USMBX1.msg.corp.akamai.com> <E78496F5-0992-4286-927C-B92FB788D8AE@gmail.com> <2A0EFB9C05D0164E98F19BB0AF3708C7130A13E5A5@USMBX1.msg.corp.akamai.com>
Date: Thu, 08 May 2014 09:31:43 -0700
Message-ID: <CABkgnnUh+Fi0SRS61iGJrBjbqHB3ZeK8uZno_X_sVJ+9GgEvHA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/WaZGIKfv5lltqKUMqSxElkfHS-Q
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] The risk of misconfiguration
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: Thu, 08 May 2014 16:31:53 -0000

On 8 May 2014 06:47, Salz, Rich <rsalz@akamai.com> wrote:
> Yes, perhaps a new alert, e_wtf, MUST/SHOULD be sent if a client offers a nonsensical combination.

I think that is actually necessary.  If you intend to prohibit
behaviour, it's best if that's enforced.  That way the chances of
non-conformant behaviour is less likely to propagate.  e_wtf sounds
like a good name.

v2.23.0 | Report a Bug | By Email