| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <01a901c45319$977372f0$0200020a@jamesnew> From: hackerwacker at cybermesa.com (james edwards) Subject: Akamai > I've just been told that it was a DoS. No details. Unlikely, Akamai is an overlay network & the root content node is not reachable. Akamai can in real time spread web traffic through out their global network of servers, diluting a DoS to the point it is not significant. It is more likely that the complexity of the overlay network was the cause. Last week it was a DNS issue and it seemed much the same this week. Provided you know the IP's of the content servers you would find they were still up. At least that was what I as seeing. Here is some info on Overlay Networks: http://nms.lcs.mit.edu/ron/ http://nms.lcs.mit.edu/ron/#papers Dr. Andersons "Mayday: Distributed Filtering for Internet Services " is quite interesting. http://nms.lcs.mit.edu/papers/mayday-usits2003/paper.html -- James H. Edwards Routing and Security Administrator At the Santa Fe Office: Internet at Cyber Mesa jamesh@...ermesa.com noc@...ermesa.com (505) 795-7101
Powered by blists - more mailing lists