wolfSSL/wolfssl
1
0
Fork 1
mirror of https://github.com/wolfSSL/wolfssl.git synced 2025-07-30 10:47:28 +02:00
Code Issues Packages Projects Releases Wiki Activity

Change the calculation for the extra data size in a DTLS message when checking to see if it'll fit in an MTU. (ZD12983)

Browse Source
This commit is contained in:
John Safranek
2021-10-01 17:35:44 -07:00
parent 34095dfd38
commit be2e7e25ac
1 changed files with 17 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
src/internal.c
View File

@ -18530,10 +18530,24 @@ int CreateOcspResponse(WOLFSSL* ssl, OcspRequest** ocspRequest,
static int cipherExtraData(WOLFSSL* ssl) static int cipherExtraData(WOLFSSL* ssl)
{ {
int cipherExtra;
/* Cipher data that may be added by BuildMessage */ /* Cipher data that may be added by BuildMessage */
return ssl->specs.hash_size + ssl->specs.block_size + /* There is always an IV. For AEAD ciphers, there is the
ssl->specs.aead_mac_size + ssl->specs.iv_size + * authentication tag (aead_mac_size). For block ciphers
ssl->specs.pad_size; * we have the hash_size MAC on the message, and one
* block size for possible padding. */
if (ssl->specs.cipher_type == aead) {
cipherExtra = ssl->specs.aead_mac_size;
/* CHACHA does not have an explicit IV. */
if (ssl->specs.bulk_cipher_algorithm != wolfssl_chacha) {
cipherExtra += ssl->specs.iv_size;
}
}
else {
cipherExtra = ssl->specs.iv_size + ssl->specs.block_size +
ssl->specs.hash_size;
}
return cipherExtra;
} }
#ifndef WOLFSSL_NO_TLS12 #ifndef WOLFSSL_NO_TLS12