-
Notifications
You must be signed in to change notification settings - Fork 11
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
Implement Channel Binding #2
Comments
@davecramer: Ping? |
@Neustradamus this is more for @ahachete to implement |
It is official, it is here: RFC 9266: Channel Bindings for TLS 1.3: |
Status update:Getting the channel-binding data from an external security layer such as that provided by TLS is out of the scope for implementation in this library, TLS channel-binding data can be fetched using a library dedicated like the Bouncy Castle Crypto APIs. Having said that, the channel binding type used by PostgreSQL is This will be included in the next major release of the SCRAM library 3.0 which is being actively worked on, but there is no ETA for a final release yet. |
@jorsol: It has been solved? |
So what do we have to do with the JDBC driver to make this work. Just update the version ? |
For the PostgreSQL JDBC Driver use, yes.
Right now is in draft, maven central is having sync issues and the jars are not available yet. Also need to check what the pipeline has to say and fix it. |
@jorsol: Good job about 3.0! Important to specify in the ticket where it has been added. |
PostgreSQL 11 will have channel binding.
We'll need to extend the TLS interface to provide access to the Finished message and the peer certificate.
The text was updated successfully, but these errors were encountered: