Skip to content

Certificate Pinning #799

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
kingmatusevich opened this issue Jan 29, 2016 · 9 comments
Closed

Certificate Pinning #799

kingmatusevich opened this issue Jan 29, 2016 · 9 comments
Labels
type:feature New feature or improvement of existing feature

Comments

@kingmatusevich
Copy link

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.

@nlutsenko
Copy link
Contributor

I agree with pinned certificates, though requiring this for everyone would probably be less than ideal, taking into account that this would explicitly require people to update their apps when a certificate expires/changes.

I would recommend changing the source code in place to allow this, since the change is relatively small and would also allow you to bundle any certificate you want if you are using self-hosted Parse Server.

@kingmatusevich
Copy link
Author

I'm not suggesting it as the only alternative, but I'm saying it should be one to allow the use of self signed roots.

@nlutsenko
Copy link
Contributor

Aha, got you.
I think the ideal API would then be as an additional property on the ParseClientConfiguration class to allow for trust policy configuration.

@adonoho
Copy link

adonoho commented Apr 16, 2016

So as to not duplicate work, is the team at Parse working on adding certificate pinning? Or is this something we should be doing to the Parse SDK as an open source project?

@markuswinkler
Copy link
Contributor

markuswinkler commented Nov 28, 2016

Any progress on this?

@nlutsenko : if you pin just the public key there is no need to update the app when a certificate expires/changes.
see here:
http://stackoverflow.com/questions/15728636/how-to-pin-the-public-key-of-a-certificate-on-ios

@acudworth
Copy link

Would be great to see this implemented asap, all too easy for a malicious user to intercept app <-> server communication at the moment

@markuswinkler
Copy link
Contributor

ping

@stale
Copy link

stale bot commented Sep 19, 2018

This issue has been automatically marked as stale because it has not had recent activity. If you believe it should stay open, please let us know! As always, we encourage contributions, check out the Contributing Guide

@stale stale bot added the wontfix label Sep 19, 2018
@stale stale bot closed this as completed Sep 26, 2018
@sunlyear
Copy link

Aha, got you.
I think the ideal API would then be as an additional property on the ParseClientConfiguration class to allow for trust policy configuration.

Can you explain how to allow this trust policy in the latest SDK?

@mtrezza mtrezza added type:improvement type:feature New feature or improvement of existing feature and removed Discussion labels Oct 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature New feature or improvement of existing feature
Projects
None yet
Development

No branches or pull requests

7 participants