-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
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
ssl: Convey alert information to passive socket operations recv and s… #8823
ssl: Convey alert information to passive socket operations recv and s… #8823
Conversation
CT Test Results 2 files 67 suites 47m 57s ⏱️ Results for commit 6e08534. ♻️ This comment has been updated with latest results. To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass. See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally. Artifacts// Erlang/OTP Github Action Bot |
ebac4cc
to
2f89b65
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
2f89b65
to
5837926
Compare
…etopts If a TLS-1.3 server fails client certification the alert might arrive in the connection state and even after data has been sent. Make sure the alert information will be available in error reason returned from passive socket API functions recv and setopt.
5837926
to
6e08534
Compare
@IngelaAndin In the Gun ticket linked just above this comment a user points out that the TLS alert may be lost in additional cases such as when calling |
…etopts
If a TLS-1.3 server fails client certification the alert might arrive in the connection state and even after data has been sent. Make sure the alert information will be available in error reason returned from passive socket API functions recv and setopt.