IETF Logo Mail Archive

Re: [TLS] Should we require implementations to send alerts?

Henrik Grubbström <grubba@gmail.com> Wed, 16 September 2015 11:51 UTC

Return-Path: <grubba@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 B77FB1ACDD9 for <tls@ietfa.amsl.com>; Wed, 16 Sep 2015 04:51:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level:
X-Spam-Status: No, score=-1.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, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] 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 6ySLHywpob2o for <tls@ietfa.amsl.com>; Wed, 16 Sep 2015 04:51:42 -0700 (PDT)
Received: from mail-la0-x241.google.com (mail-la0-x241.google.com [IPv6:2a00:1450:4010:c03::241]) (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 1E9911ACDBE for <tls@ietf.org>; Wed, 16 Sep 2015 04:51:42 -0700 (PDT)
Received: by lagj9 with SMTP id j9so12104176lag.2 for <tls@ietf.org>; Wed, 16 Sep 2015 04:51:40 -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:content-transfer-encoding; bh=zJnLAinxEA8qP6QjHZA/wRAYCIdEZYhoknf4JtN3QyU=; b=hvNxVN0bEX+q90SJHpbtRn4JizhXRTHthOexc3Ev9LgAqFZZKyZJALt8UP+sdvz1Hj V3/g9Whd+RavwFDP9TF4brG2G+rXz3VQVqqXZMJKptPXIyNjBXFwY1IETWUzZl9rFGCY 28bfYoBDsVctZ0mJs0qsAVPaO7zzys6o/BFkJpEgE96fSj4od8oGFlexwAR5e5Hbk3f2 6+8UWvwbKYdPg8SuLq+bIEsb6iXbT8WSmkEvdZAcjRSEi6nPTP3Lb+hGz0PdisOjWL0N JJ+n5/F8vUQGtTm1KiNq4/1knoStF/gioSrsp/+/qLBqaVr0fJ9vkRDg2z13HT4yh9EI LBRw==
MIME-Version: 1.0
X-Received: by 10.152.21.9 with SMTP id r9mr22001525lae.1.1442404300395; Wed, 16 Sep 2015 04:51:40 -0700 (PDT)
Received: by 10.112.252.37 with HTTP; Wed, 16 Sep 2015 04:51:40 -0700 (PDT)
In-Reply-To: <55F93E51.50001@redhat.com>
References: <CABcZeBPnO4zn_HkvwLpLC+EVYN8EKOBEsR80oRt3HZgsiNGDoQ@mail.gmail.com> <55F81AA6.2040107@redhat.com> <20150915162921.GG13294@localhost> <55F93E51.50001@redhat.com>
Date: Wed, 16 Sep 2015 13:51:40 +0200
Message-ID: <CALuAYvaTVtPf=XXC8xhFA4AEgZ=qYHH8mBSMkoWKQb+bOgniNw@mail.gmail.com>
From: Henrik Grubbström <grubba@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/tls/jp0dttWDZsS3G_tNMnAIfSugPNk>
Cc: "tls@ietf.org" <tls@ietf.org>
Subject: Re: [TLS] Should we require implementations to send alerts?
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: <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, 16 Sep 2015 11:51:43 -0000

On Wed, Sep 16, 2015 at 12:02 PM, Florian Weimer <fweimer@redhat.com> wrote:
> On 09/15/2015 06:29 PM, Nico Williams wrote:
[...]
>>
>> But if you have a fatal error you'll be closing immediately anyways.
>> Does sending the fatal alert cause a problem other than increase the
>> likelihood of RSTs?  What is the alternative considering that the next
>> step is to close the connection anyways?
>
> I'm trying to explain that any requirement to send fatal alerts will be
> difficult to implement.  With the BSD sockets API, the only way to do
> that reliable is *not* to close the socket immediately, which is
> apparently not what you (or existing APIs) expect, and which is where
> the difficulty lies.

What about SO_LINGER?

-- 
Henrik Grubbström                                       grubba@grubba.org
Roxen Internet Software AB                              grubba@roxen.com

v2.23.0 | Report a Bug | By Email