I checked this further and the issue was indeed with my code.. I did some
recent async io completion handler refactor because of which the bio's
socket write completion was triggering the observer's read completion
callback.. the records were actually client side write bio buffers which
got mixed w
I hook an observer for decrypted data immediately after the handshake is
successful (SSL_do_handshake rc 1) and it is this observer which gets the
ccs+list data on the vert next ssl_read cycle. Now, it could be that my
code is at fault here.. But I do see the decrypted dummy ccs and one more
record
On 24/11/2022 07:57, Neelabh Mam wrote:
Hi,
With my openssl based FTPS client (non-blocking bio) targeting TLS1.3, I
see that immediately after a successful data channel handshake (with
session reuse), a dummy change_cipher_spec record and a non-application
data record are sent as part of
