IETF Logo Mail Archive

Re: [TLS] PR#625: Change alert requirements

Eric Rescorla <ekr@rtfm.com> Wed, 07 September 2016 18:21 UTC

Return-Path: <ekr@rtfm.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 61C7012B252 for <tls@ietfa.amsl.com>; Wed, 7 Sep 2016 11:21:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 GcuZ2ThSoToZ for <tls@ietfa.amsl.com>; Wed, 7 Sep 2016 11:21:10 -0700 (PDT)
Received: from mail-yb0-x22c.google.com (mail-yb0-x22c.google.com [IPv6:2607:f8b0:4002:c09::22c]) (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 665A512B248 for <tls@ietf.org>; Wed, 7 Sep 2016 11:21:10 -0700 (PDT)
Received: by mail-yb0-x22c.google.com with SMTP id x93so8859493ybh.1 for <tls@ietf.org>; Wed, 07 Sep 2016 11:21:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=moMYaJBdzhj22JDK7f6vra0w39uTNlVkkRHQESopZ1Q=; b=RdFciiybRt8yah6j4JCrS6y/RdMfbSIDYNI5rHWkRgBvB0Jl49xTAQf52iXjQqkF/1 Agfhc52htHRcVTbFJcvEWnfyjvHC8UMEOY5tbeo/FfSelQ+hQELpWLDGo2WxRkePofzr Fv8cMMVXAcsgsrq/JXbXbe7tpavk1/9Qp38rXYXy6wUdvF6ouq8+KQItVBkmhuqj8HGw OJP03d5nig5ic91gQK3SXKkmYMl8H4sIxKk8ITtfODLYjAr9M4bbtgrI/FUCeyZsulSf CbMQzeeP7Jy6BG77wa3pFUFEQPiAVnBd1l3dVN9DscU/0JxyqdMp41qc435nG4yOMBhn fMrw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=moMYaJBdzhj22JDK7f6vra0w39uTNlVkkRHQESopZ1Q=; b=Mcz6Jk2cBIslDZXhoLHPb1YLKxnGBBtiBbRuLfO15S6tdcycSkZerJqe/0qKj+nND7 419WJj5CijIcVBFjlXHRqUIJwfpYO91cFwosJj2gk0UKWdVWDI5QKa2Krdo/8Dnfi7kS AIhMc+bstEWu1oO5bZqWF8IfnmMMN0leuvxs2nWMKlr3CKlgPSSbwnjQ+FSwXzRnJXq1 IISc+ypdebfA1KVj+5/9H7Y7MaOK6S1QAUeRPmwodomNgqhkft44YdJCuESTIKjJwqVw uEGZWOnsWUsN+rB/peuhIMDQXqhHtuycBZ+aJpAiA6ze6pB5PRtWIl0ra3Yh+zCQK0Rs sOYA==
X-Gm-Message-State: AE9vXwNTlz09QpPpX1DcrqWky2rmGLNxWHiuqEoO1vJB4gmr4OQmzO2B5qsC0unQP8XeZgwJSgtTRtloSju02w==
X-Received: by 10.37.215.80 with SMTP id o77mr17641938ybg.6.1473272469735; Wed, 07 Sep 2016 11:21:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.112.66 with HTTP; Wed, 7 Sep 2016 11:20:29 -0700 (PDT)
In-Reply-To: <DM2PR0301MB0847A61D65DBF3AEC2149E168CF80@DM2PR0301MB0847.namprd03.prod.outlook.com>
References: <CABcZeBMeLgqjvr2cjWL=AHTQJbS9siNBB6U2=0654yigbBGkYA@mail.gmail.com> <1558569.9rZYFBiQ0G@pintsize.usersys.redhat.com> <CABcZeBMCkSJ1nGfZDjx3CJcUsLhH4AMZ=0wOc+uNs0YKu6kW1Q@mail.gmail.com> <3902031.op4bE2I96X@pintsize.usersys.redhat.com> <DM2PR0301MB0847A61D65DBF3AEC2149E168CF80@DM2PR0301MB0847.namprd03.prod.outlook.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 07 Sep 2016 11:20:29 -0700
Message-ID: <CABcZeBNLSTMT6ARTyXAAXzHJujzxrn7Sc6NwDTSQBS8VCvqe0w@mail.gmail.com>
To: Andrei Popov <Andrei.Popov@microsoft.com>
Content-Type: multipart/alternative; boundary="94eb2c0689ac377b25053beefaef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/J2ENkg_85V14-E4K7TN3j342GW8>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] PR#625: Change alert requirements
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.17
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, 07 Sep 2016 18:21:11 -0000

On Wed, Sep 7, 2016 at 11:19 AM, Andrei Popov <Andrei.Popov@microsoft.com>
wrote:

> > > the only popular stack I found that does not seem to send alerts is
> > > the schannel from Microsoft
>
> To clarify, schannel does generate alerts per RFC, but the HTTP stack
> (which actually owns the socket) sees no value in sending them.
>

My impression is that this sometimes applies to Chrome as well.

-Ekr


> Cheers,
>
> Andrei
>

v2.23.0 | Report a Bug | By Email