Require encryption #168
Merged
Require encryption #168
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
Closes #163
DavidSchinazi
approved these changes
Apr 19, 2023
Co-authored-by: David Schinazi <DavidSchinazi@users.noreply.github.com>
achernya
approved these changes
Apr 19, 2023
gloinul
approved these changes
Apr 20, 2023
There was a problem hiding this comment.
I think the MUST can be missinterpreted. Either that one MUST always use TLS or QUIC encryption, or that what I think is actually written. TLS or QUIC MUST be used to get confidentiality, integrity and authentication. I could see this rewritten as "confidentiality, integrity and authentication is RECOMMENDED to use, to achieve this TLS or QUIC encryption is used depending on HTTP version.
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.
Closes #163