0.23.7
send_close_notify
is now idempotent, in case it is accidentally called more than once.read_tls
now refuses to read further data after aclose_notify
is received, by returningOk(0)
(ie, an EOF).- Correct fix in 0.23.6 to properly discard data after
close_notify
received, avoiding a spuriousDecryptError
on subsequent calls toprocess_new_packets()
.
What's Changed
Full Changelog: v/0.23.6...v/0.23.7