TLS1.3 change_cipher_spec as part of application data

2022-11-23 Thread Neelabh Mam
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 the directory listing data. Same holds true for

Re: TLS1.3 change_cipher_spec as part of application data

2022-11-24 Thread Neelabh Mam
15 PM Matt Caswell wrote: > > > 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),

Re: TLS1.3 change_cipher_spec as part of application data

2022-11-24 Thread Neelabh Mam
got mixed with the ssl_read data on the read path. Thanks for the pointer, we are doing good. Nothing further is needed at this point. Neelabh On Thu, Nov 24, 2022 at 4:51 PM Neelabh Mam wrote: > I hook an observer for decrypted data immediately after the handshake is > successful (SSL_d