Frédéric Lécaille

I am not sure to understand what you meant. Linux TCP statck uses its own congestion control algorithm implementations. There is no congestion control algorithm in the linux UDP stack....

@KazuyaKanemura @hloeung @osevan What do you expect from BBR? Just curious...

Haproxy did not manage to decipher the client handshake level packets but the header protections were correctly removed I guess, because the packet number start from 0. Even if non...

> Do you have any suggestion about which cipher to use ? Any of them, except the last one in the list if I remember well (too weak) which is...

What can be experienced is to decipher the ciphered packets into a debug buffer to check that haproxy can decipher the packet it has ciphered on this platform with this...

[pkt_decipher.txt](https://github.com/haproxy/haproxy/files/15354434/pkt_decipher.txt)

@lgv5 thank you! This is interesting! In fact the patch exhibits the fact that haproxy cannot decipher the packets it has ciphered. So, the issue is on haproxy+TLS stack side....

from tests directory you can run the AEAD tests as follows: ``` $ srcdir=. ./aeadtest.sh aeadtests.txt Completed 9 test cases PASS Completed 74 test cases PASS Completed 6 test cases...

botovq said there is no issue with OpenBSD+quictls.

@lgv5 It would be interesting to add this section **at the head** of aes_256_gcm_tests.txt file and to test it again as follows: `./aeadtest aes-256-gcm ./aes_256_gcm_tests.txt` from tests libressl sources directory....