Allow for TLS v1.2 when using LuaSec (not OpenResty) #58
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
|
Any Update on this? |
|
Any update on this? When are we merging these changes? |
|
Thanks, @leafo for merging this. How can I get build for this? |
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.
Adds
ssl_versionoption to user configuration. Kept default TLS version at 1.0 for backward compatibility but allow for user-specified version going forward, e.g.,"tlsv1_2". This parameter only applies to LuaSec installations—not OpenResty, which uses the Nginx Lua module built-ins for secure socket communication.Fixes #57 for non-OpenResty case.