3 ms·
The certificate is presented when fairly little information has been sent by your browser, so it's tough to target it more specifically than source IP address a
by schoen 10y ago
The certificate is presented when fairly little information has been sent by your browser, so it's tough to target it more specifically than source IP address and OS/browser.
There are a lot of ideas for catching this and some of them are starting to work, like HPKP pinning and preloads, and in the long run Certificate Transparency (including not accepting certs that haven't been publicly disclosed).
If you use HTTPS Everywhere, you have an option to submit certs that you see to the EFF SSL Observatory.
I don't mean to minimize the threat; I think there are lots of sites and browsers against which misissued certs can still be successfully used today without detection, and it's important to keep working on making that no longer true.