3 ms·
This is another one of the articles that says absolutely nothing. The only reason why such attack was possible is because some of the providers did not filter
by notyourday 9y ago
This is another one of the articles that says absolutely nothing.
The only reason why such attack was possible is because some of the providers did not filter announcements from hobos claiming to be able to advertise AWS space. That could have only happened if:
a) AWS did not register all their policy prefixes
b) providers did not apply filters on the transit announcements from those that announced AWS prefixes based on the policies registered by AWS.
This is a modern day "let residential IPs to send data directly to tcp/25 and not check".
- lathiat 9y agoIf you think the majority of BGP speakers world-wide are applying these announcement filters you are sadly mistaken.
- notyourday 9y agoI dont remember when was the last time that I was able to just announce anything I wanted either as a customer or peer to any large network. So as long as the large networks filter their customers and peers it seems to minimize the exposure. [1] [1] That statement excludes Google whose idea of filtering is to let me announce anything I want and build filters based on what I announce.