Created
September 28, 2022 00:20
-
-
Save PollyP/026ffa962a76cc44c9e287ad1dad8d1b to your computer and use it in GitHub Desktop.
Postman HTTPS proxy on Kali
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I'm using Postman on Kali. I've set up Postman as a proxy on Chrome (using FoxyProxy) and can capture requests | |
over HTTP while I interact with my target site in Chrome. Awesome! | |
Now I want to capture requests running over HTTPS. According to the Postman documentation at | |
https://learning.postman.com/docs/sending-requests/capturing-request-data/capturing-https-traffic/#installing-the-certificate-for-use-with-chrome, | |
all I need to do is install the postman-proxy-ca.crt certificate that's in ~/.config/Postman/proxy in Chrome's CA certificate | |
store ... except that postman-proxy-ca.crt doesn't exist?!? | |
According to @mjhika's comment at https://community.postman.com/t/i-cant-found-the-postman-proxy-ca-crt-certificate-in-my-computer/23177/3, | |
this is because Postman requires OpenSSL version 1.1.1.1. The July 2022 version of Kali, which is the version I'm running, | |
comes with OpenSSL version 3.0.4-2. Apparently backward compatibility is Not A Thing in this case. And, welp, the 1.1.1.1 version is not | |
available in apt list. | |
Then I looked at this thread on https://askubuntu.com/questions/1126893/how-to-install-openssl-1-1-1-and-libssl-package, and | |
read @Marmayogi's comment that gave me a link to version 1.1.1.1's source. So I was going to build this sucker: | |
wget https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/openssl/1.1.1-1ubuntu1/openssl_1.1.1.orig.tar.gz | |
tar zxvf openssl_1.1.1.orig.tar.gz | |
cd openssl-1.1.1/ | |
./config | |
make | |
make test | |
This last step reported some errors, but I kept on going to see if it would work anyway: | |
sudo make install | |
And whaddaya know, I had /usr/lib/x86_64-linux-gnu/libssl.so.1.1! | |
Now I quit Postman and restarted it ... and now had a postman-proxy-ca.crt certificate in ~/.config/Postman/proxy. Yay! | |
I followed Postman's instructions for getting the CA certifcate into Chrome's store, and switched Chrome's proxy over | |
to Postman. I enabled Postman's proxy, got a request capture going and started browsing in Chrome ... and was pleased to see my HTTPS | |
requests being captured. Yeeeeeeeeessssssss. | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment