Branch: refs/heads/feature/dtls-1.3
Home:
https://github.com/openssl/openssl
Commit: d0663981d23aca697fc9858ea5c2f5b26f852bbe
https://github.com/openssl/openssl/commit/d0663981d23aca697fc9858ea5c2f5b26f852bbe
Author: Ryan Hooper <
ryho...@cisco.com>
Date: 2025-12-12 (Fri, 12 Dec 2025)
Changed paths:
M include/internal/recordmethod.h
M ssl/d1_msg.c
M ssl/quic/quic_tls.c
M ssl/record/methods/dtls_meth.c
M ssl/record/methods/ktls_meth.c
M ssl/record/methods/recmethod_local.h
M ssl/record/methods/tls13_meth.c
M ssl/record/methods/tls_common.c
M ssl/record/rec_layer_d1.c
M ssl/record/rec_layer_s3.c
M ssl/record/record.h
M ssl/statem/extensions.c
M ssl/statem/statem_clnt.c
M ssl/statem/statem_dtls.c
M ssl/statem/statem_srvr.c
M test/helpers/ssltestlib.c
M test/sslapitest.c
Log Message:
-----------
Fixing comment out tests for DTLS1.3 in sslapitest
Several tests where commented out for the behavior of DTLS1.3 is
different then TLS1.3. The main difference is around the ACK
message. This means some tests needed to be massaged to for
the peer to ACK to a certain message.
This PR does not remove all TODO's for DTLS1.3. Currently there
are two TODOs. One around padding for messages less than 16
bytes and one for authentication and integrity only messages.
Also this PR still has a lot of memory leaks. Looking into it
it has to deal with how new record layers are allocated for
new epochs. Because record layers are also stored in a list of
messages sent in case they need to be resent it wasn't a simple
fix. I feel like the memory leaks should be tackled in a
separate PR.
Fixes:
https://github.com/openssl/project/issues/1667
Reviewed-by: Frederik Wedel-Heinen <
fwh.o...@gmail.com>
Reviewed-by: Matt Caswell <
ma...@openssl.org>
Reviewed-by: Tomas Mraz <
to...@openssl.org>
(Merged from
https://github.com/openssl/openssl/pull/29067)
To unsubscribe from these emails, change your notification settings at
https://github.com/openssl/openssl/settings/notifications