Add SPKI pinning TLS strategy (opt-in) #715
Merged
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
ok2c
approved these changes
Aug 28, 2025
Member
ok2c
left a comment
ok2c
left a comment
There was a problem hiding this comment.
@arturobernalg Same thing here. As long as you are willing to maintain this code, none of us can stop you from contributing it.
Introduce SpkiPinningClientTlsStrategy enforcing sha256(SPKI) pins post-handshake with exact/wildcard host matching. Opt-in; standard PKI and hostname verification remain in place.
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.
Introduce SpkiPinningClientTlsStrategy to enforce sha256/<base64(SPKI)> pins after standard trust-manager and hostname verification. Works with classic (setTlsSocketStrategy) and async (setTlsStrategy) clients. Opt-in only; no default behavior change.