Post: Lots posted AC...
Lots posted AC... →
Posted Tuesday 22nd July 2008 05:32 GMT
In Researcher's hypothesis may expose uber-secret DNS flaw
I'd imagine that this isn't a simple rebind like Destroy suggests, since Kaminsky spoke about that plenty at last year's DefCon.
I agree that full disclosure is the best solution in nearly every case, but if this is as potentially bad as it sounds (And I'd imagine that it is, given that Kaminsky came up with it,) then it could pose some really serious problems if it got out before much patching had happened.
And you can't very well not tell anyone that there is a problem with the major service, because so many people have to get patches installed, and there aren't that many sysadmins out that who just jump right on every patch for every service that they run.
That said - why don't we have a DNS replacement yet? I guess we'll get one right after everyone stops running SMTP.
And judging by current trends, they'll both be presentation layer protocols running over http. DNS 2.0, anyone? Maybe we can include some sort of RSS / streaming element to get some VC interested.
Most read
Popular Whitepapers
- Business-Critical Applications
The Benefits of Intel Xeon Processors and Windows Server 2008 R2 for Business-Critical Apps - Data Center Savings
Realizing Data Center Savings with an Accelerated Server Refresh Strategy - Virtualization with the Intel Xeon Processor 5500 Series
A proof of concept - The Great Virtualization Dilemma of the Next Decade
What You Need to Know - Out-of-box comparison between Dell, HP, and IBM blade servers
Receiving, unpacking and installing each system in the server rack - Real-world server consolidation with VMware vSphere 4
35 HP ProLiant DL385 servers onto 5 Dell PowerEdge M610 blade servers with VMware vSphere