I recall that subdomains are their own record inside a DNS, which would imply that anyone can claim that their server is a non-existent subdomain of the real domain
I recall that subdomains are their own record inside a DNS, which would imply that anyone can claim that their server is a non-existent subdomain of the real domain
They’d need a certificate authority to issue the certificate, and the victim’s browser would have to trust that authority.
I’ve been able to downgrade https sites to plain http sites, through a series of loopholes which I won’t go into.
So you’ve… compromised your own security. Grats?
My own security? Hah, that’s a joke right?
Everything on the Internet Archive can be accessed via simple http, even if the original archived site was https.
All that does is allow someone in the middle to potentially read your traffic. So what’s secret about the traffic between you and the Internet archive? If it’s only your login details, that seems like a you problem.
It wasn’t long ago that most of the internet was http only.
That’s nice, be sure to tell us how it goes when HSTS is enabled
Checks own servers…
Yeah, I’d like to see that…
http://web.archive.org/web/20230919001454if_/https://charleston.craigslist.org/avo/d/mount-pleasant-stealth-fighter/7667184419.html
Anything on the archive can be accessed via simple http, regardless of whether the original site was https or not.
Yeah, but now you’re talking about communicating with
web.archive.organd notnonesense.reputable-bank.comas in the original post. In this case you’re not even trying to hide the fact, that you aren’t affiliated withreputable-bank.comand we’re back to square one and you could also just usereputable-bank.com.some.malicious-phishing.websiteto host your page.Btw: all modern browsers will warn you when you access a non-encrypted website - some immediately, some only when you try to enter data into a login form.