-
Notifications
You must be signed in to change notification settings - Fork 22
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
Update TLS usage. #252
Update TLS usage. #252
Conversation
PTAL @tidoust. Also, FYI @DavidSchinazi and @pwnall as this was based on your feedback from TPAC 2019 (thank you!): |
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.
Thanks!
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.
I don't know much about TLS 1.3 internals so cannot comment on whether something might be missing, but this looks good to me and aligned with what the group discussed and resolved.
This PR addresses editorial issues #219 and #220, that were resolved to remove profile- and extension-specific information from the usage of TLS 1.3. Two parameters are retained that identify an incoming TLS connection request as intended for a specific OSP Agent.
Cipher and signature algorithm recommendations will likely be added back to this section in a later PR to close Issue #218.
Preview | Diff