Re:Hacker Redirects Traffic From 19 Internet Providers to St...
by scott_karana on Thursday August 07, 2014 @08:45PM
(#8150927)
Wow. Not sure why they don't name-and-shame the ISP, but that's really ridiculous.
[ Parent
| on HN ]
Re:Hacker Redirects Traffic From 19 Internet Providers to St...
by sergers on Thursday August 07, 2014 @09:24PM
(#8151014)
As a Canadian, using a Canadian ISP, I would like to know as well.
Not entirely surprised regarding rogue employee possibility.
Re:Hacker Redirects Traffic From 19 Internet Providers to St...
by dfox on Friday August 08, 2014 @08:53AM
(#8152524)
There are two things at play here: attacker has to have access to one ISP to inject the route (eg. rogue employee) and there has to be another ISP that accepts such route from BGP (I would say that filtering weirdly specific routes is good and common practice). When you have access to ISP network you don't have to inject things into BGP to attack your own customers.
Re:Hacker Redirects Traffic From 19 Internet Providers to St...
by devicenull on Friday August 08, 2014 @05:43PM
(#8155213)
A /24 is not a 'weirdly specific route'. I agree, that the upstream should have been filtering things, but you can't expect them to just filter out all the /24's.
For example, Google DNS anycast would stop working: http://bgp.he.net/net/8.8.8.0/24 as would basically anyone else doing anycast.
Re:Hacker Redirects Traffic From 19 Internet Providers to St...
by devicenull on Friday August 08, 2014 @05:45PM
(#8155223)
NANOG post from this morning has the AS path:
http://mailman.nanog.org/pipermail/nanog/2014-August/069131....
I'm unsure exactly which was originating the route.