IETF Logo Mail Archive

Re: [TLS] Alerts

Martin Thomson <martin.thomson@gmail.com> Wed, 10 May 2017 20:51 UTC

Return-Path: <martin.thomson@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 874FD12EAB8 for <tls@ietfa.amsl.com>; Wed, 10 May 2017 13:51:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 vnT_TgSmXxes for <tls@ietfa.amsl.com>; Wed, 10 May 2017 13:51:56 -0700 (PDT)
Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::22e]) (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 17FFF129C0B for <tls@ietf.org>; Wed, 10 May 2017 13:51:56 -0700 (PDT)
Received: by mail-wr0-x22e.google.com with SMTP id w50so5829444wrc.0 for <tls@ietf.org>; Wed, 10 May 2017 13:51:55 -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=fr9hkLgnOgIPih9ODqM+NTfYEORcIpdF6R4GVV4xUVk=; b=tqwP+qXtWtUt0WB9m5EPOiclqgmg+0N9PV34QlksolpWJEgR+jwL0zFynfqWvYTiZl /Klwm4RDIFVAyi3aeJSUGlcfn+GBguRkA8bi4yaEl0L+UWQCMhsuVw2W86wtm+bAaYRU G6x/YVFuas9fuSsm+wCZQjBnhiEKGzqL+8tbVVdnofR/gIPSw7Q4hSBZfO1i5rFcfm/+ OR+/zjK2ZLmsLqHY5G8Vv4ED7yCqgx7wL8D7Mt4fFPNjuRuI0gd23yFGGATk9AiDcJ8Z mM8JR8o+F1j62lGapMRQYq2Nbq2qTCC9Fy19xPmCi9YWrv7E2ogJN4KFgDNwu5CNIkBW QOjg==
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=fr9hkLgnOgIPih9ODqM+NTfYEORcIpdF6R4GVV4xUVk=; b=PnvkULzeiwdlGGjpeXka3nKPH87kgt9JbVQCrcTfEe8NJkQT1LYwWKj3OrwjiEgMPX dS4tzanhXo/Czd8OrZYhmkQYvca2RY/OSKX/8zrmo8RCr63TbqOHppbd0FIHnuSrwrvp jrEWJlzIjn9W52ISS3Vba3WD+HnrURikU4jWYZdWycH2u20jIOLN34aSFFWElk21K2Zo NwF8FWCyc7Dlp0PfXyIPX7FZWFEAQ70BfBN28ME/lzdZLwZ/fmxfZDP9TANpso9ajfSz Ya2zjUA/0twrhJZL5tyPuPwAyNQmrkb0/aUoSgTzVNhoA0msfRo/tkbYrIY6+8WLtEv1 5x2w==
X-Gm-Message-State: AODbwcDND9hBEhPG54PDkQX9EgwyiFC0alq9yDhyaB3vjZRK3g1bit5A +J9JNkvEBMQsEtw8KLfrbpm1DPEW79GA
X-Received: by 10.46.8.26 with SMTP id 26mr3503650lji.128.1494449514537; Wed, 10 May 2017 13:51:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.83.2 with HTTP; Wed, 10 May 2017 13:51:53 -0700 (PDT)
In-Reply-To: <CAMoSCWYokkJO7NdJ78SpviiUoZdDzD225JnS+QW0KZcVMty2Hg@mail.gmail.com>
References: <CAMoSCWYokkJO7NdJ78SpviiUoZdDzD225JnS+QW0KZcVMty2Hg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 11 May 2017 06:51:53 +1000
Message-ID: <CABkgnnVdY7esjLTPakjV6i781eFMdXbZg+PbgLoVmGLdxMh_Bg@mail.gmail.com>
To: Matt Caswell <frodo@baggins.org>
Cc: "tls@ietf.org" <tls@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/Vq1ygQrEqvCXgz6NcP9B3Kz-MBs>
Subject: Re: [TLS] Alerts
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, 10 May 2017 20:51:57 -0000

On 11 May 2017 at 01:21, Matt Caswell <frodo@baggins.org> wrote:
> Do we really need all of these alerts?

NSS uses these, but in ways that I don't really understand.  I think
that this is part of the general issue that TLS does and doesn't
really include requirements about how to handle the certificate chain.

v2.23.0 | Report a Bug | By Email