Skip to content
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

Merged
merged 3 commits into from
Mar 1, 2021
Merged

Update TLS usage. #252

merged 3 commits into from
Mar 1, 2021

Conversation

markafoltz
Copy link
Contributor

@markafoltz markafoltz commented Feb 23, 2021

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

@markafoltz markafoltz requested a review from tidoust February 23, 2021 19:11
@markafoltz
Copy link
Contributor Author

PTAL @tidoust.

Also, FYI @DavidSchinazi and @pwnall as this was based on your feedback from TPAC 2019 (thank you!):
https://www.w3.org/2019/09/15-webscreens-minutes.html#x05

Copy link

@DavidSchinazi DavidSchinazi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Copy link
Member

@tidoust tidoust left a 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants