Skip to content
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

Behavior when a third party certificate expires #28

Closed
drshock opened this issue Nov 3, 2015 · 1 comment
Closed

Behavior when a third party certificate expires #28

drshock opened this issue Nov 3, 2015 · 1 comment

Comments

@drshock
Copy link

drshock commented Nov 3, 2015

If you use this library to pin third party certificates (servers you do not own) to protect API keys and user data, will the app be bricked when the certificates from those sites eventually expire? Looking to understand if TrustKit is an approach that would avoid such pinning behavior. This would be for an app that has to support iOS 7.1.2 and up.

@nabla-c0d3
Copy link
Member

If you configure TrustKit to not enforce pinning for these domains (TSKEnforcePinning set NO), the App will work fine but you will still get reports for pinning validation failures (so you can see if your users are affected, and also detect when the certificates changed).
However, if you want to enforce pinning (ie. block connections when there's a validation failure), it is, as you said, not a good idea to do this for domains you don't own, as the certificate chain could change at any time and brick the App.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants