[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

To: "EKR" <ekr@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [TLS] Serious crypto problem fixed by envelope HMAC method instead of currently used prefix
From: "Omirjan Batyrbaev" <batyr@xxxxxxxxxxxx>
Date: Mon, 20 Nov 2006 17:51:15 -0500
Cc: TLS@xxxxxxxxxxxxxx
List-archive: <http://www1.ietf.org/pipermail/tls>
List-help: <mailto:tls-request@lists.ietf.org?subject=help>
List-id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-post: <mailto:tls@lists.ietf.org>
List-subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
List-unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
References: <><86lkm6rdau.fsf@xxxxxxxxxxxxxx><> <86d57irvjl.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxx>

>The length
> value is explicit in the record and is used to find the >record
> boundary (recall that TCP has no explicit record >boundaries).

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?

-Omirjan


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

Follow-Ups:
- Re: [TLS] Serious crypto problem fixed by envelope HMAC method instead of currently used prefix
  - From: Mike
- Re: [TLS] Serious crypto problem fixed by envelope HMAC method instead of currently used prefix
  - From: Steven M. Bellovin
- RE: [TLS] Serious crypto problem fixed by envelope HMAC methodinstead of currently used prefix
  - From: Jan Mikkelsen

References:
- [TLS] Serious crypto problem fixed by envelope HMAC method instead of currently used prefix
  - From: Omirjan Batyrbaev
- Re: [TLS] Serious crypto problem fixed by envelope HMAC method instead of currently used prefix
  - From: EKR
- Re: [TLS] Serious crypto problem fixed by envelope HMAC method instead of currently used prefix
  - From: Omirjan Batyrbaev
- Re: [TLS] Serious crypto problem fixed by envelope HMAC method instead of currently used prefix
  - From: Eric Rescorla

Prev by Date: Re: [TLS] Serious crypto problem fixed by envelope HMAC method instead of currently used prefix
Next by Date: RE: [TLS] Serious crypto problem fixed by envelope HMAC methodinstead of currently used prefix
Previous by thread: Re: [TLS] Serious crypto problem fixed by envelope HMAC method instead of currently used prefix
Next by thread: RE: [TLS] Serious crypto problem fixed by envelope HMAC methodinstead of currently used prefix
Index(es):
- Date
- Thread