Re: [TLS] question: decode_eror
Mike <mike-list@pobox.com> Wed, 20 December 2006 23:01 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxAQo-0004VO-Kq; Wed, 20 Dec 2006 18:01:02 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GxAQn-0004VJ-Tz for tls@ietf.org; Wed, 20 Dec 2006 18:01:01 -0500
Received: from proof.pobox.com ([207.106.133.28]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GxAQm-0000Bn-Nj for tls@ietf.org; Wed, 20 Dec 2006 18:01:01 -0500
Received: from proof (localhost [127.0.0.1]) by proof.pobox.com (Postfix) with ESMTP id 87BCC28CAB for <tls@ietf.org>; Wed, 20 Dec 2006 18:01:22 -0500 (EST)
Received: from [192.168.1.8] (wsip-24-234-114-35.lv.lv.cox.net [24.234.114.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by proof.sasl.smtp.pobox.com (Postfix) with ESMTP id 50D5CA2935 for <tls@ietf.org>; Wed, 20 Dec 2006 18:01:22 -0500 (EST)
Message-ID: <4589C0DD.60302@pobox.com>
Date: Wed, 20 Dec 2006 15:01:49 -0800
From: Mike <mike-list@pobox.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: tls@ietf.org
Subject: Re: [TLS] question: decode_eror
References: <BAY103-W80B3FF63BB87F4CB9B1D492CF0@phx.gbl>
In-Reply-To: <BAY103-W80B3FF63BB87F4CB9B1D492CF0@phx.gbl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc:
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Errors-To: tls-bounces@lists.ietf.org
> how does one "abort the handshake", in each case? > > For example:- Does one send handshake_failure alert, at warning or > fatal? Lets assume warning. I think that fatal is what is intended. > Upon "abort the handshake", does the updated TLS1.1 standard require > either client or server > implementations to perform a warning-level close_notify? close_notify is for graceful shutdown; I don't think you need to send it after a fatal alert is sent. Mike _______________________________________________ TLS mailing list TLS@lists.ietf.org https://www1.ietf.org/mailman/listinfo/tls
- [TLS] question: decode_eror Peter Williams
- RE: [TLS] question: decode_eror Peter Williams
- Re: [TLS] question: decode_eror Mike
- Re: [TLS] question: decode_eror Mike