I forgot to mention that I was running the application in VMplayer with a NAT network; the pavement removed the problem with the initial handshake, but sometimes after reconnecting it saw the same message; using the method in Sam’s connection, he received an “unexpected record” during a handshake - Google said this error was a revision, but this was not so; digging in OpenSSL sources: the new connection used the same BIO to read and receive application data from the previous connection I don’t know how to reset the SSL structure with asio, so dynamic allocation of sockets using the new | delete
source share