4/14/2026 at 2:47:38 AM
Tom appears to have totally missed SSLStrip.Before browsers screamed bloody murder over http, a MITM could defeat SSL by acting as the SSL endpoint and forwarding everything as plain http. And back then, the only indication was lack of a 16px lock icon and a missing "s" in "https".
It's additionally daft to think that just because the page is public knowledge, a specific person reading the page is never sensitive information. As a blunt example, Wikipedia is obviously public knowledge. If you are a Chinese national reading https://en.wikipedia.org/wiki/1989_Tiananmen_Square_protests... then the CCP might like to know your location.
by toaste_
4/14/2026 at 5:31:04 AM
Indeed, this is something not discussed in an otherwise very good article.As explained in the article, using HTTPS provides very little protection against whoever operates the site to which you are connecting, who might still not be who you think they are, despite accepted certificates.
Nevertheless, using HTTPS, especially when not transmitting any non-encrypted information, like the name of the site for which the connection is requested, protects you from those third parties who are not able to intercept your outgoing connections and act as middlemen, but who might still monitor your traffic and attempt to record it or to interfere with it.
by adrian_b
4/14/2026 at 2:16:03 PM
Privacy and security are not synonymous. Though it would have been nice to have the ideas discussed in the video.by bitbasher