-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/11/2012 01:53 PM, francis.daigneault@bell.ca wrote:
It's the easy answer to avoid admitting they where DDOS, when you can't explain something or you don't want to admit something blame it on "corruption" The outages start and stop at the time predicted by the hacker who "admit" it.. how could that happen.. coincidence ?
What if 'corruption' in this case meant 'tampering'? Is it possible that their routing tables were corrupted either by injection or someone compromising a router and reconfiguring it? It's been a few years since I last heard about route injection (at DefCon, wasn't it?) so I don't know whether or not it's widely possible, or at least plausible in the case of GoDaddy. - -- The Doctor [412/724/301/703] [ZS] Developer, Project Byzantium: http://project-byzantium.org/ PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F DD89 3BD8 FF2B 807B 17C1 WWW: https://drwho.virtadpt.net/ Back off, man. I'm a sysadmin. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlBQw/oACgkQO9j/K4B7F8GjewCeIFgLDJFRuQjYyzzclDrPIAqR sH0AoIeu0tYe/6ZozcOJD6RcS/GfG9G+ =DYwF -----END PGP SIGNATURE-----