Adjust and generalize cached_info guidance. #270
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now that we've switched to encrypting the entire ClientHello, there's nothing wrong with cached_info in ClientHelloOuter, provided it's based on the public name rather than the inner name. And, more generally, name-specific extensions take some care. Replace the prohibition with more general guidance in Security Considerations, with cached_info merely being an example. This addresses issue tlswg#266.
chris-wood
approved these changes
Aug 17, 2020
Co-authored-by: Christopher Wood <caw@heapingbits.net>
Co-authored-by: Christopher Wood <caw@heapingbits.net>
Co-authored-by: Christopher Wood <caw@heapingbits.net>
chris-wood
approved these changes
Aug 17, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that we've switched to encrypting the entire ClientHello, there's
nothing wrong with cached_info in ClientHelloOuter, provided it's based
on the public name rather than the inner name. And, more generally,
name-specific extensions take some care.
Replace the prohibition with more general guidance in Security
Considerations, with cached_info merely being an example.
This addresses issue #266.