Difference between revisions of "Intercept SSL Traffic"

From WebOS Internals
Jump to navigation Jump to search
Line 31: Line 31:
 
Edit /etc/hosts
 
Edit /etc/hosts
 
10.0.2.1 <target-host>
 
10.0.2.1 <target-host>
 +
 +
 +
openssl s_client -connect <target-host>:<target-port> -showcerts
 +
 +
copy the PortSwigger server CA cert into /etc/ssl/certs/trustedcerts/PortSwigger.pem
 +
 +
link it into /etc/ssl/certs/trustedcerts/ and /var/ssl/trustedcerts/ as <hash>.0
 +
 +
openssl x509 -hash < PortSwigger.pem

Revision as of 10:21, 27 March 2011

Run Internet Sharing on your host, gateway address is 10.0.2.1, client wifi address is 10.0.2.x

Run burpsuite (must be run as root)

Assumes you want to intercept traffic to <target-host>:<target-port>

proxy listeners

  • local listener port: 443
  • listen on loopback interface only: no
  • support invisible proxying for non-proxy-aware clients: yes
  • redirect to host: <target-host>
  • redirect to port: <target-port>

server SSL certificate

  • generate a CA-signed certification with a specific hostname: <target-host>

intercept client requests

  • intercept-if: yes
  • update Content-Length: yes

intercept server responses

  • intercept-if: yes
  • update Content-Length: yes

misc

  • unpack gzip / deflate: yes

On the device

Edit /etc/hosts 10.0.2.1 <target-host>


openssl s_client -connect <target-host>:<target-port> -showcerts

copy the PortSwigger server CA cert into /etc/ssl/certs/trustedcerts/PortSwigger.pem

link it into /etc/ssl/certs/trustedcerts/ and /var/ssl/trustedcerts/ as <hash>.0

openssl x509 -hash < PortSwigger.pem