New answers tagged


If it gets resources from a site like a CDN the certificate will be verified against the URL of this resource, in this case the CDN. The URL of the HTML file embedding these resources does not matter in this case, only the URL of the resource itself. ... with a protocoless path A path like //host/page instead of http://host/page or https://host/page ...


You could try running synflood against port 443. The client wouldn't be able to connect, and may fail back to port 80. Just a disclaimer, but I haven't tried this. Anyone want to chime in?


I figured it out. To do this, you need to download the latest version of Wireshark source code. I ran my test on Wireshark 2.0.1 You need to make changes to the file - /epan/dissectors/packet-ssl-utils.c in the Wireshark source folder. Print the variables to a file from line 3179 - 3194. You can find the Client write key, Server write key, Client MAC ...


SSLStrip+ works without deleting browser data too. The script needs a fake DNS server to work, in fact modifying DNS queries you have an huge possibility to bypass HSTS. So you don't need to clear your data. Also HSTS depends on the HTTP request header, so for example when you navigate to Google you make a GET request and the response header says to the ...


The six keys are derived from the master secret, the client random and the server random. You can get the master secret and the client random from the SSLKEYLOGFILE. I suppose you can sniff the server random with Wireshark from the server key exchange message. If you have those, you can call some library function or script on them to get the six keys. The ...


Those sites (and some more) use public key pinning with HSTS, whereas the browser does not accept other certificates or a downgrade to http.

Top 50 recent answers are included