

So it looks like this workaround is a bust for me.ġ. And the certificate doesn't even work: I'm getting the same "This Connection Is Not Private" error. But although the Burp landing page shows when I visit I'm not seeing any Proxy traffic at all in HTTP history. When I upgraded again to 2020.4.1, I was able to successfully import the custom certificate into Burp. When I go to import this file into Burp on 2020.2, I ran into the IllegalArgumentException error described here: key file, and then reused it when creating the.
Paw mac app ssl trust cert password#
I set a password of my own choosing on the. $ openssl pkcs12 -export -out BurpRootCA.pfx -inkey myBurpCA.key -in root-ca.crt $ openssl req -new -x509 -days 365 -key myBurpCA.key -out root-ca.crt -subj "/C=CA/O=Burp/OU=Certification Services/CN=MyBURPRootCA/" $ openssl genrsa -aes256 -out myBurpCA.key 4096 I tried following the steps above to generate my own 365-day certificate as above: I'll let you know if I discover anything else. I hope we can identify a workaround swiftly. At least I found this thread, thanks Liam for being so active here. I don't want to be fighting with my tools. Gotta be honest, this is super frustrating. OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.6+10, mixed mode) OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.6+10) Clearly, Burp is in place or I wouldn't get the Burp error. This worked previously, so I don't know what's wrong now. When I tried to roll back to 2020.2 Pro, visiting on the device results in this Burp error page: "Error: Unknown host: burpsuite". I often get requests and responses listed in the HTTP history in Burp, but the apps balk. Chrome and Firefox have the same problem, along with every other app.

When I go to any https site, though, I get "This Connection is Not Private" in Safari.
Paw mac app ssl trust cert install#
I can successfully install the Burp CA on the device. It's jailbroken with checkra1n, though that shouldn't make a difference. In the meantime, I had upgraded from 2020.2 Community Edition and I'm now on iOS 13.5. I tried to fire up the proxy again today after not touching it for awhile. I have previously done lots of iOS proxying via Burp with a previous iOS version (I think it was 13.3.1) and previous versions of Burp.
