B
Premium,MVM
join:2000-10-28
1 edit | reply to SUMware
Re: Exploit Code for Kaminsky DNS Bug Goes Wild
Uh, guys, if the whole point is that DNS can no longer be trusted, and you're recommending things to people, does it make sense to direct them to sites by their DNS name?
You've referred above to:
»www.theregister.co.uk/2008/07/24···es_wild/
and
»caughq.org/main.html
and
»www.caughq.org/exploits/CAU-EX-2008-0003.txt
and
»www.caughq.org/exploits/CAU-EX-2008-0002.txt
and
»www.doxpara.com
and
»www.opendns.com
At this writing, unless my current DNS resolvers are being attacked, these latter two resolve to »157.22.245.20 and »208.67.219.99, respectively.
Insanely, sadly, and hilariously however, the Kaminsky Doxpara site appears to be on a shared host and cannot be accessed by IP address!
Oops, you got the default vhost. Call LC support.
If anyone knows how to access the Doxpara.com site by its web host's IP address as a customer sub-page or whatnot, perhaps they should mention it...
Edit: Equally distressingly, »https://www.doxpara.com/ (SSL) does not resolve either; at least that would have been a trustworthy way to access the URL. I haven't followed this vulnerability at all, but I assume a cert (that you verify) is still an easy way to allay one's fears?
-- B
--
In a realm outside causality and function |
