RE: [TLS] Serious crypto problem fixed by envelope HMAC methodinstead of currently used prefix

["Jan Mikkelsen" <janm@xxxxxxxxxxxxxxxxxxx>]

Omirjan Batyrbaev wrote:
> >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?

No.

TCP provides a reliable byte stream service.  As stated in the message you
are responding to, TCP has no explicit record boundaries.  Specifically, an
implementor of any TCP based service (including TLS) should not assume that
recipient reads will match sender writes.

What happens with TCP packets depends on many variables. These are
irrelevant to TLS and are hidden by a TCP implementation.

TLS has a record layer to provide a record abstraction on top of TCP.

Regards,

Jan Mikkelsen


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