 FiOS DanPremium
join:2001-07-06
Redondo Beach, CA | With DNS Flaw Now Public, Attack Code Imminent "One day after a security company accidentally posted details of a serious flaw in the Internet's Domain Name System (DNS), hackers are saying that software that exploits this flaw is sure to pop up soon." (More...).
--
Courage is being scared to death but saddling up anyway.
|
|
|
|
 Its a SecretPlease speak into the microphonePremium
join:2008-02-23
Da wet coast
kudos:3 | Nice. The idiot from Matasano should be shown the door. And this from a security company?
--
"In the future, that which is not madatory will be illegal" |
|
 sivranBack to Opera againPremium
join:2003-09-15
Arlington, TX
kudos:1 | reply to FiOS Dan
Bring it on. My network's ready.  |
|
 CabalPremium
join:2007-01-21
Austin, TX | reply to FiOS Dan
»DNS Critical Flaw Explained? |
|
 JohnInSJPremium
join:2003-09-22
San Jose, CA | reply to FiOS Dan
Re: With DNS Flaw Now Public, Attack Code Imminent OpenDNS, and just about every other DNS has been patched already. This was more a media event then anything else.
--
My place : »www.schettino.us |
|
Its a SecretPlease speak into the microphonePremium
join:2008-02-23
Da wet coast
kudos:3 | Perhaps they all were playing catchup, but good to see the fix is in place!
--
"In the future, that which is not mandatory will be illegal" |
|
| reply to FiOS Dan
To be safe from this flaw: does one need to patch the local systems in addition to using a DNS server that's safe from this flaw. |
|
 amysheehanPremium,VIP,MVM
join:1999-12-21
Huntington Beach, CA
kudos:9
 ·RoadRunner Cable
| reply to JohnInSJ
said by JohnInSJ:OpenDNS, and just about every other DNS has been patched already. This was more a media event then anything else. SoCal Road Runner's DNS servers have NOT [as of this writing] been secured.
Hopefully all this RR slowdown stuff happening won't keep them from allocating the resources to resolve this issue which IMO should be Job 1.
-amy-
--
Proud Member of ASAP
DSLR Phishtracker |
|
 jbobReach Out and Touch SomeonePremium
join:2004-04-26
Little Rock, AR | reply to JohnInSJ
said by JohnInSJ:OpenDNS, and just about every other DNS has been patched already. This was more a media event then anything else. According to this thread: »Change your DNS away from AT&T NOW!!!
AT&T DNS servers are not patched either. If true that's pretty lame and dangerous. |
|
 SteveI know your IP addressConsultant
join:2001-03-10
Yorba Linda, CA
kudos:5 | reply to FiOS Dan
You guys are all idiots - I've been invulnerable to this for a long time.
I just use a really really really really big hosts file |
|
SUMwarePremium
join:2002-05-21
kudos:2
3 edits | reply to FiOS Dan
DNS Randomness Tests DNS Resolver(s) Tested:
208.69.32.14 (bld4.ash.opendns.com) appears to have GREAT source port randomness and GREAT transaction ID randomness.
The essence of the problem is that DNS resolvers don't always use enough randomness in their transaction IDs and query source ports. Increasing the amount of randomness increases the difficulty of a successful poisoning attack.
This page exists to help you learn if your ISP's nameservers are vulnerable to this type of attack. If you click on the button below, we will test the randomness of your ISP DNS resolver.
For test visit: »www.dns-oarc.net/oarc/services/dnsentropy
The test takes a few seconds to complete. When its done you'll see a page where the transaction ID and source port randomness will be rated either GREAT, GOOD, or POOR. If you see a POOR rating, we recommend that contact your ISP and ask if they have plans to upgrade their nameserver software before August 7th. |
|
TheWiseGuyDog And ButterflyPremium,MVM
join:2002-07-04
Yonkers, NY
kudos:1 Reviews:
·Optimum Online
| Re: With DNS Flaw Now Public, Attack Code Imminent Thanks for the link.
OOL seems to have just patched, the link indicated they had done it right, versus dox which indicated possible NAT. Looks as if they use a larger sample.
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore. |
|
 caffeinatorComing soon to a cup near you..Premium
join:2005-01-16
WA, USA
kudos:3
 ·CenturyLink
| reply to SUMware
Re: DNS Randomness Tests Nice one..the other test never did work on my machine.
However, using my primary DNS server from the ISP I get:
Source Port Randomness: POOR (one port used but it's a high range)
Transaction ID Randomness: GREAT (25 diff. ID's used)
So, is that a problem?
I use openDNS as my secondary as a failsafe FWIW.
-CaFF |
|
LibraPremium
join:2003-08-06
USA
kudos:1 | reply to SUMware
I did this test twice on my 98se computer and got this:
1. 68.237.161.37 appears to have POOR source port randomness and GREAT transaction ID randomness.
2. 68.237.161.38 appears to have POOR source port randomness and GREAT transaction ID randomness.
The first time I did this test the results were the same but the number was 68.237.161.36.
I also did the test on our XP computer which has the MS Patch, and AOL running - AOL came up great for both tests, but my dsl numbers (similar to above) had the same poor source port and great randomness.
I have Verizon DSL with the Westell 2200 modem (that has a NAT Firewall router) and I use a switch to connect both pcs.
When Dan Kaminsky first had his test both computers tested "your dns server appears safe". After he changed the test, both computers show "your NAT is interfering".
I don't understand all of this. How do I fix this (or does Verizon have to fix this)? Also, I don't know how to switch to an open DNS.
Thank you.
Sincerely, Libra |
|
TheWiseGuyDog And ButterflyPremium,MVM
join:2002-07-04
Yonkers, NY
kudos:1 Reviews:
·Optimum Online
| To switch to opendns follow the instructions in Section 4 of the link below (instructions quoted) for windows 98 and use the following IP addresses for DNS servers, (ignore the Domain instructions and the gateway instructions.)
208.67.222.222
208.67.220.220
»Satellite Forum FAQ »[DW4000] I'm sharing my connection on a LAN. Do I need to do more?
said by faq :
Windows 98:
Start => Settings => Control Panel => click on the Network icon or right-click on the Network Neighborhood icon and choose 'Properties'. Either way gets you into the Network configuration screens.
From the list of installed clients, protocols and services, locate TCP/IP bound to the NIC It will look something like this: TCP/IP -> your network card. The arrow indicates the protocol is bound to that adapter. Highlight that and then click the Properties button. This gets you into the TCP/IP configuration screens. Click the DNS Configuration tab. Put as dot in the 'Enable DNS' radio button.
Then add the DNS servers,
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore. |
|
| reply to FiOS Dan
Re: With DNS Flaw Now Public, Attack Code Imminent said by FiOS Dan:"One day after a security company accidentally posted details of a serious flaw in the Internet's Domain Name System (DNS), hackers are saying that software that exploits this flaw is sure to pop up soon." (More...). I would question whether that release was accidental. Seems more like it was done on purpose because they were annoyed that they weren't given all the info and part of the "in-crowd" that Kaminsky gave the info to.
--
My BLOG .. .. Internet News .. .. My Web Page
Ask yourself one question: 'Do I feel lucky?' Well, do ya punk? |
|
1 edit | reply to JohnInSJ
Good test to check your ISPs DNS servers said by JohnInSJ:OpenDNS, and just about every other DNS has been patched already. This was more a media event then anything else. If you want to check whether your ISPs DNS servers are updated, you can run this test.
»entropy.dns-oarc.net/test/
It tests for BOTH port randomness and Transaction ID randomness.
I use Opendns and they showed GREAT on both tests. But my ISPs DNS(Comcast) that I use as the 3rd DNS entry in my list showed as POOR on the port randomness test.
--
My BLOG .. .. Internet News .. .. My Web Page
Ask yourself one question: 'Do I feel lucky?' Well, do ya punk? |
|
jbobReach Out and Touch SomeonePremium
join:2004-04-26
Little Rock, AR | FYI The OARC test may not be as accurate on Comcast. See this thread:
»[DNS] Comcast and the DNS Server flaw issue
Even Dan Kaminsky has chimed in. |
|
| Thanks for update. I did try the doxpara test too. But the doxpara test only tests the 1st DNS server it finds in the DNS list for the computer. The entropy test tests all the entries in the computers DNS list. So that made it easier to use.
In any case, the opendns servers test as well as or better than Comcasts and I'll stick with them.
--
My BLOG .. .. Internet News .. .. My Web Page
Ask yourself one question: 'Do I feel lucky?' Well, do ya punk? |
|
