Implement Maximum Fragment Length TLS extension

[clementperon]

It seems that Libressl doesn't support maximum fragment length negotiation extension : https://tools.ietf.org/html/rfc6066#page-8

A patch has been posted on openssl group https://groups.google.com/d/msg/mailing.openssl.dev/fQxXvCg1uQY/_g09FmmhvgwJ

Could you review and integrate it for 2.5.X release ? This will be very usefull for embedded clients who can't allocate big buffer in RAM.

Thanks,

[4a6f656c]

Do you have an actual use case for this? If so, could you please provide further details.

[clementperon]

Yes instead of several call on a server i would like to receive one "big" json (around 8Ko) and parse it on the go. I am not able to allocate more than 2ko of RAM for TLS.

[bob-beck]

In what application?

On Tue, Aug 30, 2016 at 03:08:50AM -0700, Cl??ment Peron wrote:

Yes instead of several call on a server i would like to receive one "big" json (around 8Ko) and parse it on the go. I am not able to allocate more than 2ko of RAM for TLS.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
#214 (comment)

[clementperon]

IOT device (cortex M4, 128ko RAM)

[bob-beck]

So this is not a public application. Do you know if OpenSSL is taking that patch?

On Tue, Aug 30, 2016 at 04:15:08AM -0700, Cl??ment Peron wrote:

IOT device

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#214 (comment)

[clementperon]

The patch is planned to be merged post 1.10 : openssl/openssl#1008

[rojer]

+1 on this. it is very important for IoT connectivity where 16K contiguous allocation requirement is a problem. OpenSSL already supports this.