{"author":"Jay Satiro","author_email":"raysatiro@yahoo.com","author_time":1755670253,"commit_time":1755841828,"committer":"Jay Satiro","committer_email":"raysatiro@yahoo.com","hash":"b6a5f672597a06bdf4361a2e70bb53c6f097105f","message":"schannel: improve handshake procedure\n\n- During handshake, do not require reading more data if unprocessed\n  encrypted data that may be a complete TLS record is already available.\n\n- During handshake, check that the socket is writeable before processing\n  encrypted data that may require an immediate reply to the server.\n\nThese two fixes are for issues that were found during renegotiation\ntesting but could affect any handshake.\n\nPrior to this change it was possible in some abnormal network conditions\nfor the Schannel TLS handshake procedure to erroneously wait or error.\n\nRef: https://github.com/curl/curl/pull/18125\n\nCloses https://github.com/curl/curl/pull/18323\n","parents":["7d5f535ca722c32699484751c37f9883f02358b3"],"tree_hash":"41f45755a39d5b42563f07047806bfa6caa5d76b"}