Question: working around unsigned short assignment on TLSrecord length about scapy-ssl_tls HOT 2 CLOSED

Hi @perrin-ay,

There is tls_fragment_payload which allows to fragment records on whatever boundary you wish. I understand that that's not really what you're after, but worth mentioning ;)

I don't think what you're trying to do will work, because the record length field is dictated by the spec. So even if you increase it's size, the receiving end will still read it as a 3 byte field.
Generally with TLS fragmentation, the interesting use cases I have seen are around fragmenting the handshake across multiple records. The max record size (214) and max handshake size (216) are different, which leads to some interesting edge cases.

Cheers,
Alex

from scapy-ssl_tls.

Hi @alexmgr

Apologies for opening this issue. I realized the mistake in my query moments after hitting submit and subsequently closed the case.

But thank you for your attention and input.

If you are interested , to give some background on what i was looking at , at the time, was to draw out a plan to trigger this ASSERT in openssl
https://github.com/openssl/openssl/blob/master/ssl/s3_cbc.c#L170

I had to step away from this and onto other things , but time permitting will get back to it soon.

Thanks again!

from scapy-ssl_tls.