Open the Local Certificate Management Console that you setup earlier. If you followed the directions, this should be in the C:\certs folder. In this case I configure the proxy as 192.168.234.182Ĭopy the FiddlerRoot.cer file from the Proxy Computer to this computer. ![]() Setup the browser to use the Proxy System While there are tricks and drivers you can install to get around this, the options seem to be somewhat impractical (IMHO) for general use or involve paid software. In other words, if I have two processes communicating on the same computer, you need to use something else to capture the traffic between them.Ĭheck out the following articles for additional discussion around this as well as alternatives: Also consider using a capture filter to limit the traffic to only what you are interested in.īefore moving on to the client computer I would like to explain why I am using two computers – why not do everything from the same computer? In short, because I couldn’t figure out how to get it to work! In Windows, you cannot capture network traffic that goes through the loopback (local) interface – at least not with WinPcap. Note: For prolonged network captures, consider using tshark or dumpcap instead. Start a network capture on Wireshark on the correct interface. ![]() Ssl_init private key file c:\certs\msappsrv-fiddler.ukey successfully loadedĪssociation_add TCP port 443 protocol http handle 02E13BF0 If you open it up you should see a successful key load:ġ92.168.234.182,443,http,c:\certs\msappsrv-fiddler.ukey So in the RSA keys list I enter: 192.168.234.182,8888,http,c:\certs\msappsrv-fiddler.ukeyįor the SSL debug file I use the same directory as the key: c:\certs\ssldebug.logĪs soon as you click OK, Wireshark will create the ssldebug log file. In this example, the local system has an IP Address of 192.168.234.182, the SSL Port is 8888 (the proxy port for Fiddler), the protocol is http, and the path to the private key is c:\certs\msappsrv-fiddler.ukey In Windows XP, the Desktop directory is located under “Documents and Settings” and so it will not work.Ĭlick on the + box next to Protocols to open the listįor the RSA keys list, enter the following: Local (Proxy) System IP Address, SSL Port, Protocol, and Path to the unencrypted private key Note: This is important - the SSL preferences in Wireshark cannot handle a space in the path. 7BlxxDuLHhbytM3/Ba1A3VBjYxNqZeHkl3MJrmp2sS6cw=Ĭreate a folder in the root of the C:\ drive called certs and move all the certificate, PFX, and key files to this directory. MIICXgIBAAKBgQDMyzpyOm+xAR0lzc11JlXZgMQ9Parz6g/4X8Z+Ok/FaHvK4kez Verify the results – the file should look similar to this: Note: When it asks for the pass phrase enter the password you just used You should now have a Management Console that looks like this: My sure Local Computer is selected and click Finish This time select Computer Account and click Next Make sure My User Account is selected and click FinishĪgain, make sure Certificates is selected and click Add Setup a Local Certificate Management Console: I had to install the Visual C++ 2008 Redistributables to get OpenSSL to install correctly. ![]() ![]() Wireshark (and WinPcap) – Network AnalysisĪssuming Internet Explorer 8 on both computersĭownload and install the current version of Wireshark along with the included version of WinPcap:ĭownload and install the current version of Fiddler:ĭownload and install the current version of OpenSSL:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |