-
-
Notifications
You must be signed in to change notification settings - Fork 342
Certificate Pinning #218
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
Comments
@montymxb @kingmatusevich is this issue closed? |
@davidtavarez Nope, it is still open and still something we are happy to implement in the future; but no work has started on this yet. |
Doesn't What other types of SSL/TLS check would be needed? (That would support both cURL and stream_context). |
This can be achieved by creating your own HTTP client and pass in your SSL/TLS options
https://github.com/parse-community/parse-php-sdk#http-clients We could add |
For those interested I added an example for public key pinning, cert fingerprint checking, peer verification in PHP and JavaScript (not really a thing in javascript but useful) using self signed certs #513 |
The SDKs should be compatible with pinned certificates for connecting to the Parse Servers, allowing for faster, safer deployment, particularly in small or internal deployments.
The text was updated successfully, but these errors were encountered: