Erroring out on (some?) iOS11 devices (boringssl error) about ssl-kill-switch2 HOT 4 CLOSED

@samyk I'm on iOS 10 and I have noticed the behavior where just enabling SSL kill switch breaks SSL, even when supplying a valid MITM certificate. However I saw this in only a specific app that I suspect is doing extra steps to prevent reverse engineering. In a different app, SSL kill switch works fine without supplying proper certificate for mitm proxy. Interestingly, it seems whether tls_helper_create_peer_trust returns errSecSuccess always or returns the original_tls_helper_create_peer_trust value does not matter.

edit: I could not see any reference to "boring_ssl" in app logs. I believe that's a non-apple SSL library so SSL kill switch would not handle hooking it properly.

from ssl-kill-switch2.

Interesting -- try grepping for boringssl instead of boring_ssl. I believe CFNetwork calls libboringssl which then calls one of the hooked functions, but I'll validate.

from ssl-kill-switch2.

I could not find any mention of boringssl on iOS 10 in the console logs. It could have changed for iOS 11.

from ssl-kill-switch2.

I won't have time to go back and look at iOS 11, but I added support for iOS 12 just now. To do that, I had to patch a function specifically to bypass the error returned by BoringSSL that you mentioned: ": Function boringssl_session_finish_handshake: line 2643 The peer was not authenticated. Disconnecting the connection.".
After silencing it I was able to bypass pinning validation.

from ssl-kill-switch2.