For triggering the Chrome MiTM software interstitial in the wild, we've settled that mitm-software.badssl.com with preloaded HSTS should do.
Rough outline for Sasha:
Create ca-mitm-software.crt and ca-mitm-software.key like we did did for local testing, with a common name like BadSSL MITM Software Test. Look for ca-superfish.crt and ca-superfish.key and place the new files next to them, respectively.
Create a copy of all the other files/folders with superfish in the name, where superfish is replaced with mitm-software.
Replacesuperfish with mitm-software in the contents of these files. The values you're editing should correspond to various copied files youv'e created.
Copy the superfish section in certs/Makefile with a mitm-software-replaced section.
If something goes wrong, I would start with domains/known-bad/mitm-software.conf and try to track down anything that looks like a broken reference to another file.
For triggering the Chrome MiTM software interstitial in the wild, we've settled that
mitm-software.badssl.com
with preloaded HSTS should do.Rough outline for Sasha:
ca-mitm-software.crt
andca-mitm-software.key
like we did did for local testing, with a common name likeBadSSL MITM Software Test
. Look forca-superfish.crt
andca-superfish.key
and place the new files next to them, respectively.superfish
in the name, wheresuperfish
is replaced withmitm-software
.superfish
withmitm-software
in the contents of these files. The values you're editing should correspond to various copied files youv'e created.superfish
section incerts/Makefile
with amitm-software
-replaced section.If something goes wrong, I would start with
domains/known-bad/mitm-software.conf
and try to track down anything that looks like a broken reference to another file.