IETF Logo Mail Archive

Re: [TLS] Serious crypto problem fixed by envelope HMAC method instead of currently used prefix

Mike <mike-list@pobox.com> Tue, 21 November 2006 00:28 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GmJUl-0007yd-BC; Mon, 20 Nov 2006 19:28:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GmJUk-0007yU-5z for TLS@lists.ietf.org; Mon, 20 Nov 2006 19:28:14 -0500
Received: from proof.pobox.com ([207.106.133.28]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GmJUh-0004ZY-VN for TLS@lists.ietf.org; Mon, 20 Nov 2006 19:28:14 -0500
Received: from proof (localhost [127.0.0.1]) by proof.pobox.com (Postfix) with ESMTP id 35E4123FAF for <TLS@lists.ietf.org>; Mon, 20 Nov 2006 19:28:07 -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 E4E6294C2E for <TLS@lists.ietf.org>; Mon, 20 Nov 2006 19:28:06 -0500 (EST)
Message-ID: <456247F6.60106@pobox.com>
Date: Mon, 20 Nov 2006 16:27:34 -0800
From: Mike <mike-list@pobox.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: TLS@lists.ietf.org
Subject: Re: [TLS] Serious crypto problem fixed by envelope HMAC method instead of currently used prefix
References: <006001c70c4b$3d624780$87a85e41@pbo8f8e10aowa><86lkm6rdau.fsf@delta.rtfm.com><002401c70cb5$c0a410a0$55aa5e41@pbo8f8e10aowa> <86d57irvjl.fsf@raman.networkresonance.com> <00d001c70cf6$62957a80$55aa5e41@pbo8f8e10aowa>
In-Reply-To: <00d001c70cf6$62957a80$55aa5e41@pbo8f8e10aowa>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
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

> Slightly OT: when client/server writes the TLS fragment or/and messages the
> TCP then puts it in one TCP packet? So it becomes one TCP packet per one TLS
> fragment. Is this what happens in the real world implementations?

A TLS fragment can be up to 16383 bytes, plus some extra data.  A TCP
packet is usually around 1500 bytes or less, so you will normally see
a fair amount of fragmentation.

Mike

_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls

v2.31.3 | Report a Bug | By Email | System Status