]> git.ipfire.org Git - thirdparty/openssl.git/commit
Don't apply max_frag_len checking if no Max Fragment Length extension
authorMatt Caswell <matt@openssl.org>
Tue, 2 Jan 2024 16:48:43 +0000 (16:48 +0000)
committerMatt Caswell <matt@openssl.org>
Thu, 18 Jan 2024 15:22:12 +0000 (15:22 +0000)
commit141365d1b4ab9d2ea4c76938f83b26429f0fb8ad
tree7560bb31ca00d0039e7f776eaddff9faf176068c
parent523d1233f1feda9d7561441b332600148a468d8a
Don't apply max_frag_len checking if no Max Fragment Length extension

Don't check the Max Fragment Length if the it hasn't been negotiated. We
were checking it anyway, and using the default value
(SSL3_RT_MAX_PLAIN_LENGTH). This works in most cases but KTLS can cause the
record length to actually exceed this in some cases.

Fixes #23169

Reviewed-by: Tomas Mraz <tomas@openssl.org>
Reviewed-by: Neil Horman <nhorman@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/23182)

(cherry picked from commit c1decd62460072082833909a962892e5042b16bb)
ssl/record/methods/tls_common.c