4 ms·
https://google.com/amp/hackme.com https://google.com/amp/hackme.com redirects to hackme.com. The attacker here used tiny.cc to be more elusive. IIRC we had a p
by wav-part 10y ago
https://google.com/amp/hackme.com https://google.com/amp/hackme.com
redirects to hackme.com. The attacker here used tiny.cc to be more elusive. IIRC we had a popular discussion here about this.
How google can still allow this is beyond me.
- sjeanpierre 10y agoWow this is really fucked up. Most people would automatically trust a link from Google.
- acqq 10y agoAnd the link really results in the real connection to the real Google server, which then merily redirects to wherever. Whover allowed that in Google, using the main google.com domain, what was he thinking? For me, that is the major story here.
- tmzt 10y agoWow, this should at least be googleusercontent.com or the like. It seems amp started as a whitelist of well-known publishers and morphed into somthing like an open proxy.
- acqq 10y agoEnded as the www.google.com becoming the redirector, by default, to anything, without having any query in the URL syntax. It broke what people knew how www.google.com behaved for more than a decade. But if I understood correctly it started from the idea "Google hosts your pages (if I understand correctly, even the scripts!) now with Google's TLS certificate and on Google's www.google.com domain" which is also quite fracked up for what can be expected of www.google.com?