Exploit for DNS Cache Poisoning - RELEASED
jared at puck.nether.net
Wed Jul 23 22:33:30 CDT 2008
On Wed, Jul 23, 2008 at 11:01:11PM -0400, Patrick W. Gilmore wrote:
> That did not even occur to me.
> Anyone have a foolproof way to get grandma to always put "https://" in
> front of "www"?
> Seriously, I was explaining the problem to someone saying "never click
> 'OK'" when this e-mail came in and I realized how silly I was being.
The problem is there is no perfect solution to these challenges
that the industry faces.
The enhanced SSL certs and browser magic, eg:
www.paypal.com w/ Firefox3 gives a nice green "happy" bar.
If you don't invest in these, or if there is a lack of user
education around these issues it's just one big Pharming pool.
I talked to some govvies today and made what I believe is
the clear case when it comes to "Doing the right thing(tm)". My
case was that the industry would do the right thing as a whole.
There would be stragglers, but the risk of doing nothing is too
If your nameservers have not been upgraded or you did
not enable the proper flags, eg: dnssec-enable and/or dnssec-validation
as applicable, I hope you will take another look.
Jared Mauch | pgp key available via finger from jared at puck.nether.net
clue++; | http://puck.nether.net/~jared/ My statements are only mine.
More information about the NANOG