Add an option to require client TLS certificates and verification #64
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
|
This should be followed up with a |
|
Closing as this is unlikely to be merged. |
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 adds an additional TLS flag
-client-authwhich can take on these values:none- the default, do not require client certificates:tls.NoClientCerttls.ClientAuthTyperequire- require a cert but don't validate:tls.RequireAnyClientCertverify- require and validate client cert:tls. RequireAndVerifyClientCertMaybe
tls.VerifyClientCertIfGivenwould be better than therequireone here. Or we can just allow them all.Fixes #41