feat: support tls-server-end-point channel binding for SCRAM-SHA-256 #1181
+164
−8
Conversation
This file contains hidden or 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
This comment was marked as spam.
This comment was marked as spam.
arp242
force-pushed
the
conrad/scram-sha-256-plus
branch
from
cff584e to
f316640
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Postgres supports "channel bindings" for SCRAM-SHA-256 authentication. This prevents certain MITM attacks. This authentication is known as "SCRAM-SHA-256-PLUS".
Postgres supports the "tls-server-end-point" channel binding form which is derived by hashing the raw bytes of the first certificate sent by the server in the TLS handshake.
Postgres also supports "requiring" channel binding. This additionally prevents a MITM sending cleartext the chosen authentication mechanism.
Related to #1145