02-20-2019, 07:39 PM
(This post was last modified: 02-20-2019, 07:49 PM by Codehunter.)
(02-18-2019, 07:16 PM)rlebeau Wrote: OnStatusInfo/Ex is fired at different stages of the connection, including the start and end of a handshake. You are not trying to write your file on every stage, are you?
What is stopping you from doing that today? OnStatusInfoEx gives you notification when the handshake is finished (the AWhere parameter is SSL_CB_HANDSHAKE_DONE), whether it was successful or not (the ARet parameter), and direct access to OpenSSL's SSL/TLS session object (the ASslSocket parameter).
This is what I'm tried to do here. I have seen that OnStatusInfoEx is multiple fired and the neccessary arrays are not filled at every stage. AWhere=SSL_CB_HANDSHAKE_DONE is a good hint, this was the detail what I've been missing. As I said before, I'm not a SSL expert. Currently I'm checking every time if the arrays are filled and if so, my NSS file is ready to write.
But: You said that OnStatusInfoEx is not a good idea to do this because for future changes related to OpenSSL 1.1 and TLS 1.3. This is what stopped me today :-) (The prior issue which stopped me was the byte offset) Therefore please understand me right: A request to have a similar event like OnStatusInfoEx in "Indy 11" / future development.