We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rustls::ConnectionCommon::complete_io
rustls::ConnectionCommon::complete_io could fall into an infinite loop based on network input
rustls
0.21.10
>=0.23.5,>=0.22.4, <0.23.0,>=0.21.11, <0.22.0
If a close_notify alert is received during a handshake, complete_io does not terminate.
close_notify
complete_io
Callers which do not call complete_io are not affected.
rustls-tokio and rustls-ffi do not call complete_io and are not affected.
rustls-tokio
rustls-ffi
rustls::Stream and rustls::StreamOwned types use complete_io and are affected.
rustls::Stream
rustls::StreamOwned
See advisory page for additional details.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
rustls
0.21.10
>=0.23.5,>=0.22.4, <0.23.0,>=0.21.11, <0.22.0
If a
close_notify
alert is received during a handshake,complete_io
does not terminate.
Callers which do not call
complete_io
are not affected.rustls-tokio
andrustls-ffi
do not callcomplete_io
and are not affected.
rustls::Stream
andrustls::StreamOwned
types usecomplete_io
and are affected.See advisory page for additional details.
The text was updated successfully, but these errors were encountered: