5 ms·
A JavaScript-Based DDoS Attack as Seen by Safe Browsing
- mey 11y agoThey don't identify the network operator they mention. I wonder if this is to prevent an international incident...
- nickodell 11y agoOr, they don't have any more information on that than anyone else, and they don't want to drag their discussion off-topic.
- adanto6840 11y agoFrom TFA: "At the HTTP level seen by Safe Browsing, we cannot confidently attribute this attack to anyone. However, it makes it clear that hiding such attacks from detailed analysis after the fact is difficult."
- javajosh 11y agoOut of curiosity did the Safe Browsing people notice the DDOS at all while it was happening, or did you just use the news item as justification to poke through some historical data?
- SoftwareMaven 11y agoIf this was done by China, would TLS everywhere really have prevented them from performing this attack? Couldn't they perform a TLS MITM, spoofing Baidu to people outside the GFoC. They would have the ability to modify the DNS records that show up outside China and certainly would have a CA they, effectively, control to provide a Baidu cert. They could proxy the request through to the real Baidu, then inject the JS to whatever comes back before passing it on. To the user outside China, everything looks copacetic. It is certainly a more difficult attack, but it doesn't seem like it's outside the realms of possibility for a state actor that funnels all content through one pipe. Am I overlooking something?
- petermonsson 11y agoThe attack would still be possible, but the attacker would now risk their CA status.
- deleted 11y ago[deleted]