Repository navigation
|
Got a hyper v virtual machine hosting a website on the same private subnet as my host machine. I used mkcert on the virtual machine and installed the certificate on my host machine. My host machine can connect to the website using https but as soon as i activate foxy proxy for burp suite, the browser returns "Your connection is not private". Why is this happening and is there any way i can prevent it? |
Replies: 2 comments 1 reply
|
That's Burp, not mkcert. When the browser goes through Burp, Burp terminates the TLS connection itself and hands the browser a certificate signed by its own CA (PortSwigger CA). Your host trusts the mkcert root, not Burp's, so the browser warns. Two ways out:
Only trust Burp's CA in a browser profile you use for testing: whoever holds that CA key can impersonate any site to that browser. |
|
FOUND A FIX: I remembered that i had been able to intercept request 6 months ago and the only thing i did differently back then was using virtual hosts + including 127.0.0.1 when generating the cert. When i had this problem, i wasn't using a vhost and had generated the cert for the VMs static IP + localhost. So i created a vhost and generated a cert for the VMs static IP + localhost + 127.0.0.1 + vhost domain name. The problem got solved but I'm not sure whether the fix was using a vhost or including 127.0.0.1 when creating a cert. |
FOUND A FIX:
I remembered that i had been able to intercept request 6 months ago and the only thing i did differently back then was using virtual hosts + including 127.0.0.1 when generating the cert.
When i had this problem, i wasn't using a vhost and had generated the cert for the VMs static IP + localhost.
So i created a vhost and generated a cert for the VMs static IP + localhost + 127.0.0.1 + vhost domain name. The problem got solved but I'm not sure whether the fix was using a vhost or including 127.0.0.1 when creating a cert.