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.
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
Add TLS/SSL backend: Windows Schannel #3867
Add TLS/SSL backend: Windows Schannel #3867
Changes from 14 commits
e7e4ace
bb5853a
e57d4a8
8cafc33
3245fed
0095be7
68e5650
76fe133
aed522b
7e87d3c
fcb55f5
5b31f80
8fec190
f044db6
51379b9
2d55fba
9f50c22
30a23a5
e9d470b
43cc47a
ae1c9ec
d9e2552
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Since this can potentially be used for iOS and Android in the future, perhaps have a quick look at their key stores as well, to make sure that our API and struct are compatible for future extension (in other words, so that we don't need to create a new API such as
pj_ssl_cert_load_from_store2()
).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.
Right, had a thought about this a bit, that's why
pj_ssl_cert_load_from_store()
uses an 'expandable' parampj_ssl_cert_lookup_criteria
for future use.Nevertheless, tried to do a bit research for Android. From here, it seems that a cert (& its private key) cannot be extracted out to be used by third-party security lib (such as OpenSSL), so the keystore seems to be for native SSL backend only. And from here, it looks like accessing cert in the keystore system is done via UI prompt dialog for the user selecting the cert to use, then application can assign an "alias" (perhaps some kind of "friendly-name" on Windows) for the cert for future use (so app don't need to show the UI prompt dialog again). So if in the future we have a native Android SSL backend, perhaps
pj_ssl_cert_load_from_store()
can be used to lookup TLS cert using the "alias". Thepj_ssl_cert_lookup_criteria
&pj_ssl_cert_load_from_store()
may not be able to handle any access auth though, which can be password, PIN, biometrics, etc.