SSL: separate CA file #335
Closed
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 commit allows using a separate file to specify the CA to trust. This way we have two files (cert, key) for our own certificate and one file with the trusted CA. Putting the own certificate and the CA in the same file, as previously done with the tls_cert option, does not seem to work.
|
@bluerise This is the way NGINX, Apache, and everything else I have ever used works..... It is so much more clear. +1 |
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.
This commit allows using a separate file to specify the CA to trust.
This way we have two files (cert, key) for our own certificate and
one file with the trusted CA. Putting the own certificate and the CA
in the same file, as previously done with the tls_cert option, does
not seem to work.