Skip to content

Certificate Pinning #1103

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

Open
markuswinkler opened this issue Feb 7, 2017 · 6 comments
Open

Certificate Pinning #1103

markuswinkler opened this issue Feb 7, 2017 · 6 comments
Labels
type:feature New feature or improvement of existing feature

Comments

@markuswinkler
Copy link
Contributor

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.

This issue has already been posted here but there has been no progress for over a year on this:
#799
(thanks @kingmatusevich)

My daily security newsletter is full of apps that got hacked because of a man in the middle attack which could be easily prevented if the Parse SDK allowed for certificate pinning.

@QuynhNguyen
Copy link

+1 for this task. @markuswinkler What is the daily security newsletter that you are subscribing to? I would love to know. Also, is there any short-term solution beside using the built-in ACL/CLP?

@markuswinkler
Copy link
Contributor Author

markuswinkler commented Feb 8, 2017

@QuynhNguyen I have different sources, hackernews (https://news.ycombinator.com) is pretty good, also heise.de (although german).
Latest big reveal: https://medium.com/@chronic_9612/76-popular-apps-confirmed-vulnerable-to-silent-interception-of-tls-protected-data-2c9a2409dd1

One workaround (in theory) could be to implement a cloud code test function on the server that is called via the rest interface with e.g. Alamofire (where you can pin the certificate) at a given time interval plus every time the apps awakes from the background. The cloud function itself can be empty and just return success.
In case you detect something suspicious you automatically log the user out and report it.

Disadvantages of this approach:

  • additional load on the application server
  • SDK request still vulnerable

Another workaround is to use the REST interface with Alamofire for all security sensitive calls but that could be prohibitively tedious depending on your architecture.

@markuswinkler
Copy link
Contributor Author

Maybe someone from the community can implement it?

@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
@rostopira
Copy link

@Stale It should be open (=

@gytiskv
Copy link

gytiskv commented Jan 25, 2021

#1598

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

6 participants