openssl/ssl/record/methods
Matt Caswell 5c476976ab Handle app data records from the next epoch
It is possible that DTLS records are received out of order such that
records from the next epoch arrive before we have finished processing the
current epoch. We are supposed to buffer such records but for some reason
we only did that for handshake and alert records. This is incorrect since
it is perfectly possible for app data records to arrive early too.

Fixes #20597

Reviewed-by: Tomas Mraz <tomas@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/20628)
2023-03-31 09:14:24 +01:00
..
build.info Move tls_pad.c into ssl/record/methods 2022-11-14 07:51:17 +00:00
dtls_meth.c Handle app data records from the next epoch 2023-03-31 09:14:24 +01:00
ktls_meth.c Extend the new_record_layer function 2023-01-24 17:16:29 +00:00
recmethod_local.h Rationalize FIPS sources 2023-02-08 16:20:55 +01:00
ssl3_cbc.c Rationalize FIPS sources 2023-02-08 16:20:55 +01:00
ssl3_meth.c Rationalize FIPS sources 2023-02-08 16:20:55 +01:00
tls1_meth.c Rationalize FIPS sources 2023-02-08 16:20:55 +01:00
tls13_meth.c Rename SSL3_RECORD to TLS_RL_RECORD 2022-11-14 07:51:26 +00:00
tls_common.c Remove spurious error queue entries on early data 2023-03-06 08:35:17 +11:00
tls_multib.c Rename SSL3_BUFFER to TLS_BUFFER 2022-11-14 07:51:25 +00:00
tls_pad.c Rationalize FIPS sources 2023-02-08 16:20:55 +01:00
tlsany_meth.c Rename SSL3_RECORD to TLS_RL_RECORD 2022-11-14 07:51:26 +00:00