IETF Logo Mail Archive

Re: [hybi] Fwd: failed TLS handshake: which close code?

"Richard L. Barnes" <rbarnes@bbn.com> Mon, 24 October 2011 16:07 UTC

Return-Path: <rbarnes@bbn.com>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96CDF21F8CA4 for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 09:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3zEQLRn7W23e for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 09:07:37 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 92A3421F8876 for <hybi@ietf.org>; Mon, 24 Oct 2011 09:07:37 -0700 (PDT)
Received: from ros-dhcp192-1-51-60.bbn.com ([192.1.51.60]:57354) by smtp.bbn.com with esmtps (TLSv1:AES128-SHA:128) (Exim 4.74 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1RIN3m-0003KU-7P; Mon, 24 Oct 2011 12:07:34 -0400
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: "Richard L. Barnes" <rbarnes@bbn.com>
In-Reply-To: <634914A010D0B943A035D226786325D42D0B036E9D@EXVMBX020-12.exch020.serverdata.net>
Date: Mon, 24 Oct 2011 12:07:33 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <D5E88D14-C13E-490D-933E-6B133BAF98E3@bbn.com>
References: <634914A010D0B943A035D226786325D42D0B036D6D@EXVMBX020-12.exch020.serverdata.net> <CADkeqZXXRkXCRrONLr5thwOqNVUxNWU0Q-9E0R0i=4S-bc-LFw@mail.gmail.com> <CADkeqZXDvu-JY8aZHJJPRH-_JnF196JjA_JG6X_1yrYSiAekuA@mail.gmail.com> <0ED03DDD-1AF9-41F9-B5F0-2968BF16E378@zaphoyd.com> <CADkeqZVvU31ML8tDAeYwnndvPZ9W8vEuzJksBm-4d1qv7MWObw@mail.gmail.com> <634914A010D0B943A035D226786325D42D0B036E9D@EXVMBX020-12.exch020.serverdata.net>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
X-Mailer: Apple Mail (2.1084)
Cc: "hybi@ietf.org" <hybi@ietf.org>, Peter Thorson <webmaster@zaphoyd.com>
Subject: Re: [hybi] Fwd: failed TLS handshake: which close code?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Oct 2011 16:07:38 -0000

This is pointless.  These codes are not needed by the WS API, since a TLS failure does not provide a close code.  These codes are not needed by the WS protocol, since neither party will send a close frame (since there's no TLS channel).  

--Richard


On Oct 24, 2011, at 11:24 AM, Tobias Oberstein wrote:

> TLS handshake failure codes proposal:
> 
> 1014/ TLS Handshake Failed By Client : The TLS handshake was failed by the client (unspecific).
> 
> 1015/TLS Handshake Failed By Server : The TLS handshake was failed by the server (unspecific).
> 
> 1016/TLS Handshake Failed By Client - Invalid Server Certificate :  The TLS handshake was failed by the client due to the server certificate being invalid or not accepted.
> 
> 1017/TLS Handshake Failed By Server - Invalid Client Certificate : The TLS handshake, where the server requested a client certificate, was failed by the client due to the client certificate being invalid or not accepted.
> 
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi

v2.23.0 | Report a Bug | By Email