TrustKit: Tried to generate the SPKI hash for an unsupported key algorithm
Hi,
The exception
Tried to generate the SPKI hash for an unsupported key algorithm
happens a lot to a very small amount of our users. Is this a bug or is TrustKit doing its job against potential hackers?
Thanks,
Avi
Call stack:
0 CoreFoundation 0x1848d2d8c __exceptionPreprocess
1 libobjc.A.dylib 0x183a8c5ec objc_exception_throw
2 TrustKit 0x10453ba40 -[TSKSPKIHashCache hashSubjectPublicKeyInfoFromCertificate:] (TSKSPKIHashCache.m:67)
3 TrustKit 0x10453b188 verifyPublicKeyPin (ssl_pin_verifier.m:71)
4 TrustKit 0x104542a88 -[TSKPinningValidator evaluateTrust:forHostname:] (TSKPinningValidator.m:126)
5 TrustKit 0x104542e9c -[TSKPinningValidator handleChallenge:completionHandler:] (TSKPinningValidator.m:203)
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 15 (4 by maintainers)
Ouch.
It was a bug in one of our Apps which was accidentally using the IP address of the router itself in some URL’s that were supposed to access an accessory on the local network.
So, no MITM after all…
Problem solved!
@nabla-c0d3 Hi, we’ve recently started to use TrustKit for public key pinning in our app and have also been seeing this crash happen for a small amount of users.
Are there any other scenarios where this can happen, apart from using a self-signed certificate (which we don’t)? I’m guessing it could happen if you’re trying to use the app while on an unsecure network, but users are reporting that it also happens while using mobile data. Could there be any other reasons why this crash occurs?