Re:China's Man-On-the-Side Attack on GitHub
by cbsmith on Tuesday March 31, 2015 @04:04AM
(#9294912)
One solution that comes to mind for this is for CDN's to have an edge node just outside of the great firewall of China. Even with a simple edge side include, the impact on Github's servers should be near zero.
[ Parent
| on HN ]
Re:China's Man-On-the-Side Attack on GitHub
by cxseven on Tuesday March 31, 2015 @04:17AM
(#9294953)
This won't work because it's browsers outside of China that are being hijacked when browsing Baidu Analytics-using sites.
Re:China's Man-On-the-Side Attack on GitHub
by cbsmith on Tuesday March 31, 2015 @06:02AM
(#9295260)
That's a fair point...
Still, this is a read-based DoS. It should be fairly easy to mitigate with a CDN...
Re:China's Man-On-the-Side Attack on GitHub
by encoderer on Tuesday March 31, 2015 @11:26AM
(#9296924)
Putting a dynamic app like Github behind a CDN with page-caching just does not work. Sure they could freeze those projects and serve what is now essentially static HTML, but in day-to-day operations you're left using CDN products that let you serve static parts separately from dynamic parts, which is probably of dubious benefit during a DoS attack.
Re:China's Man-On-the-Side Attack on GitHub
by cbsmith on Tuesday March 31, 2015 @07:47PM
(#9300654)
Github has got a bit of a read mostly situation. If read requests where funneled so that there was only one per URL per edge node at any given point in time (which edge side includes effectively gives you), it would make for pretty easy to manage load for Github.