SCRAM-SHA256-PLUS with tls-server-end-point channel binding #31
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
sunng87
force-pushed
the
feature/scram-plus
branch
3 times, most recently
from
ad6c233 to
7ec59a5
Compare
sunng87
force-pushed
the
feature/scram-plus
branch
from
7ec59a5 to
5114fd6
Compare
This was referenced Nov 17, 2023
|
@sunng87: Good job! Can you add RFC 9266: Channel Bindings for TLS 1.3 support too? Linked to: |
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.
This patch implements
SCRAM-SHA256-PLUSwithtls-server-end-pointchannel binding. It uses server certificate for channel binding. TLS is required when usingSCRAM-SHA256-PLUS