Closed hexploitable closed 8 years ago
Hi,
Thanks for the report. I can see that you are using kTSKSwizzleNetworkDelegates
; how are you opening the connection (which API)? The best way to use TrustKit is to manually call into TSKPinningValidator
instead of relying on kTSKSwizzleNetworkDelegates
.
Thanks,
Hey, not got the source on me right now but i was using NSURLSession
and just making a basic connection to a site via HTTPS.
Tonight i'll confirm if the behaviour is the same for the config approach + also see if I have better luck using TSKPinningValidator
.
I just tried myself on an iOS 10 device and didn't see any problems. Please re-open this issue if it's still an issue.
@hexploitable any feedback on this ? i have the same problem, also no notifications is posted (kTSKValidationCompletedNotification)
Are you using swizzling or not?
@nabla-c0d3 yes i do. the problem was i gave the domain with the protocol "https://mydomain.com" instead of "mydomain.com"
@nabla-c0d3 How do I verify that pinning is working fine? I recently Implemented Trustkit for ios but unable to understand if I need to store the SSL certificate in my app bundle or not? Please reply quick. I have a delivery today. Another question is does trust kit support API calling? or I have to use Afnetworking to call API?
any updates?
I have tried this on both iOS 9.3 Simulator + device iOS 10. Installed via pods, latest version (i.e.
pod 'TrustKit'
).I also tried adding breakpoints in the Trust Kit pin validation routines and they are never hit and as you'll see below, no logs either.
Just to see what happens, I left the default programmatic config in for my domain, with another domain's hashes (yahoo.com's hashes):
When I run the app, it actually connects to the domain anyway, despite pinning enforced, and the logs show this:
Any ideas what I might be doing wrong? Will try the
Info.plist
config route when I get the chance to see if I observe the same behaviour.