Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

yeah but the likelihood of this is incredibly remote. It would shock me if ISPs didn't have alarms going off if RFC1918 space was suddenly routable within their BGP table.

Not to mention the return packet would be NAT'd so the attacker would have to deal with that complication.





The return packet wouldn't be NATed, because stateful NAT tracks connections and only applies NAT to packets that belong to outbound connections.

Arguing over how likely this is is missing the point. If it can happen at all when you're running NAT, then it should be clear that NAT isn't providing security.


You're missing the part where the ISP is the one doing it

Mm. Can you give an example of that happening in real life?

Google "Eagerbee"

Not finding anything saying that ISPs have anything to do with Eagerbee.

ISPs were the vector for Eagerbee. Don't trust your next-hop router.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: