-
Notifications
You must be signed in to change notification settings - Fork 2.1k
feature: support load private key with password #973
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
Closed
Closed
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
2dc8e74
feature: support load private key with password
detailyang e520238
style: align
detailyang c3b9a38
tests: move password test to new .t
detailyang 1a1162f
revert t/140-ssl-c-api.t to old version
detailyang 5c60231
style: remove unused whitespace
detailyang ab2d04f
style: add blank line for .t file
detailyang a42f837
tests: optimize add_block_preprocessor
detailyang cacdcfa
rename 151-luajit.t and 141-ssl-c-api-password.t
detailyang 66d45b8
set ngx_http_lua_ssl_password_callback is static
detailyang File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about reuse the current
ngx_http_lua_ffi_priv_key_pem
andpwd == NULL
means without password?So that we can reuse most of the code.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@doujiang24 I have considered the
ngx_http_lua_ffi_priv_key_pem
. But there are some existing tests which are rely on it. I'm not sure it's worth to change thengx_http_lua_ffi_priv_key_pem
. So just add the new apingx_http_lua_ffi_priv_key_pem_to_der_with_password
, then reimplement the Lua FFI APIngx.ssl.priv_key_pem_to_der
to support passwordSo if we almost agree to reimplement the
ngx_http_lua_ffi_priv_key_pem
, I will try to do :D