IETF Logo Mail Archive

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

Tobias Oberstein <tobias.oberstein@tavendo.de> Mon, 24 October 2011 15:24 UTC

Return-Path: <tobias.oberstein@tavendo.de>
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 87FBD21F8EB2 for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 08:24:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 To9DLBuPxATO for <hybi@ietfa.amsl.com>; Mon, 24 Oct 2011 08:24:45 -0700 (PDT)
Received: from EXHUB020-4.exch020.serverdata.net (exhub020-4.exch020.serverdata.net [206.225.164.31]) by ietfa.amsl.com (Postfix) with ESMTP id 9486C21F8EB1 for <hybi@ietf.org>; Mon, 24 Oct 2011 08:24:44 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.230]) by EXHUB020-4.exch020.serverdata.net ([206.225.164.31]) with mapi; Mon, 24 Oct 2011 08:24:44 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Alexey Melnikov <alexey.melnikov@isode.com>, Peter Thorson <webmaster@zaphoyd.com>
Date: Mon, 24 Oct 2011 08:24:42 -0700
Thread-Topic: [hybi] Fwd: failed TLS handshake: which close code?
Thread-Index: AcyST5tpCCU5wmykQI+wo/5Vbug1wwAEJdnw
Message-ID: <634914A010D0B943A035D226786325D42D0B036E9D@EXVMBX020-12.exch020.serverdata.net>
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>
In-Reply-To: <CADkeqZVvU31ML8tDAeYwnndvPZ9W8vEuzJksBm-4d1qv7MWObw@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "hybi@ietf.org" <hybi@ietf.org>
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 15:24:45 -0000

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.

v2.23.0 | Report a Bug | By Email