From 2860d1460076c44da310cc595480a8ca69e07d1d Mon Sep 17 00:00:00 2001
From: Tim Perry <pimterry@gmail.com>
Date: Thu, 19 Oct 2023 21:49:53 +0200
Subject: [PATCH] Remove OkHttp <v3 and TrustKit hostname verification patches

Looks like they're actually the same implementation, it's just that
TrustKit inlined OkHttp's version.

These aren't required, as they doesn't implement certificate pinning,
and it's trivial to work around with any functional MitM setup: you
just have to return valid certs with the right hostnames. No need to
mess with that, best to check it properly, so dropped.
---
 android-certificate-unpinning.js | 26 --------------------------
 1 file changed, 26 deletions(-)

diff --git a/android-certificate-unpinning.js b/android-certificate-unpinning.js
index 7c82864..598d986 100644
--- a/android-certificate-unpinning.js
+++ b/android-certificate-unpinning.js
@@ -162,34 +162,8 @@ const PINNING_FIXES = {
         }
     ],
 
-    'com.squareup.okhttp.internal.tls.OkHostnameVerifier': [
-        {
-            methodName: 'verify',
-            overload: ['java.lang.String', 'java.security.cert.X509Certificate'],
-            replacement: () => RETURN_TRUE
-        },
-        {
-            methodName: 'verify',
-            overload: ['java.lang.String', 'javax.net.ssl.SSLSession'],
-            replacement: () => RETURN_TRUE
-        }
-    ],
-
     // --- Trustkit (https://github.com/datatheorem/TrustKit-Android/)
 
-    'com.datatheorem.android.trustkit.pinning.OkHostnameVerifier': [
-        {
-            methodName: 'verify',
-            overload: ['java.lang.String', 'javax.net.ssl.SSLSession'],
-            replacement: () => RETURN_TRUE
-        },
-        {
-            methodName: 'verify',
-            overload: ['java.lang.String', 'java.security.cert.X509Certificate'],
-            replacement: () => RETURN_TRUE
-        }
-    ],
-
     'com.datatheorem.android.trustkit.pinning.PinningTrustManager': [
         {
             methodName: 'checkServerTrusted',