$ valgrind --leak-check=full ./client
==18674== Memcheck, a memory error detector
==18674== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==18674== Using Valgrind-3.16.0.GIT and LibVEX; rerun with -h for copyright
info
==18674== Command: ./client
==18674==
ZS\!Uڃȕe;+UbH1XF
汹S
Could you please try to re-run the client via Valgrind?
On Fri, Jun 12, 2020 at 7:03 AM Xinzhe Wang wrote:
> When KTLS is enabled, multiple client's handshake will lead to unexpected
> eof while reading and data corrupt(possible memory leak).
>
> Tested OpenSSL version: master, 3.0.0-alpha1
> Ke
When KTLS is enabled, multiple client's handshake will lead to unexpected
eof while reading and data corrupt(possible memory leak).
Tested OpenSSL version: master, 3.0.0-alpha1
Kernel version: 5.4.43-1-MANJARO
Reproduce step(using docker):
sudo modprobe tls
git clone https://github.com/openssl/op
