[Tool]ProxyRegistryEditor - Edit Registry via proxy (using Windows Insider as target)

[titi66200]

Not working for me with latest windows-insider

 

[ADeltaX]

The ONLY way we will be able to get it working with the latest insider app is if we had the cert that's being sent from the response that returns the flights.

EDIT: ohhh.. This is it. The wpflights.trafficmanager.net.cer is the one . Let's see what we can do (although I don't know how far we can get with just purely a .cer).

So far I've intercepted and set the client certificate to the one it's looking for in OnBeforeRequest and OnBeforeResponse. That = no go.

Someone will figure it out

The problem is Fiddler send the certificate to the server, not to the client (Will still use the autogenerated certificate "DO_NOT_TRUST").
I tried:

string path = "location of the certificate"
oS.oResponse["https-Client-Certificate"] = path;
Fiddler.FiddlerApplication.oDefaultClientCertificate = new X509Certificate(path);

 

[snickler]

The problem is Fiddler send the certificate to the server, not to the client (Will still use the autogenerated certificate "DO_NOT_TRUST").
I tried:

string path = "location of the certificate"
oS.oResponse["https-Client-Certificate"] = path;
Fiddler.FiddlerApplication.oDefaultClientCertificate = new X509Certificate(path);

Yup, I tried something very similar.

 

[snickler]

Not working for me with latest windows-insider

Nope. It only works with the version before the 2/19 update. The code has changed to make this method useless (until we find a way to trick it)

 

[snickler]

The problem is Fiddler send the certificate to the server, not to the client (Will still use the autogenerated certificate "DO_NOT_TRUST").
I tried:

string path = "location of the certificate"
oS.oResponse["https-Client-Certificate"] = path;
Fiddler.FiddlerApplication.oDefaultClientCertificate = new X509Certificate(path);

Now that I think of it.. I don't see a way around this at all since we don't have the cert. Once we decrypt the process, it automatically uses the DO_NOT_TRUST cert for this process. No way we can decrypt and set request cert (It's not looking at ClientCerts at all) with Fiddler without the cert that's needed.

 

[ADeltaX]

Now that I think of it.. I don't see a way around this at all since we don't have the cert. Once we decrypt the process, it automatically uses the DO_NOT_TRUST cert for this process. No way we can decrypt and set request cert (It's not looking at ClientCerts at all) with Fiddler without the cert that's needed.

An idea is to use Fiddler as Reverse proxy.
Redirect url to a local server (for example using WAMP) and use OpenSSL.

 

[snickler]

An idea is to use Fiddler as Reverse proxy.
Redirect url to a local server (for example using WAMP) and use OpenSSL.

That was something I started on. Using it as a Reverse Proxy and then having a local IIS Server handling the response and sending the X509Cert.. Also would probably have to involve setting wpflights.trafficmanager.net to your hosts file to point to 127.0.0.1. I don't know IF it will actually work though, but it's worth a shot.

Try it out