Newsletters Select newsletters below and click the button to sign up!
Internetnews BloggersRecent Entries
ArchivesMonthly ArchivesSearch The Blog
« Red Hat opens up the cloud with Deltacloud |
Sean Michael Kerner Blog
| Qwest moving to 100 GbE by 2010 »
.edu getting secured with DNSSECFrom the 'Securing Education' files:
DNSSEC is the smart, educated way to secure DNS right? Ever since security researcher Dan Kaminsky big DNS security disclosure in 2008, the need for DNSSEC, which provides integrity security for DNS information has been obvious. Yet relatively few top level domains (TLDs) have actually signed their zones for DNSSEC. The .edu (for education) TLD, operated by Educause is now set to join the ranks of DNSSEC secured TLDs by March of 2010. A testbed is set to be in place this month to begin the preliminary work. Educause manages the .edu TLD under an agreement with the U.S Department of Commerce. "The Internet plays a vital role in higher education by facilitating online learning, collaboration, and research," said Lawrence E. Strickling, Assistant Secretary for Communications and Information at the Department of Commerce in a statement. "We are pleased that DNSSEC will be implemented in the .edu domain, which complements work already underway to better secure the Domain Name System overall."This is clearly good news and further adds to the momentum that DNSSEC is now enjoying. From my vantage point, I see 2010 as the year of DNSSEC with the beginning of wide adoption. I still think it will take a year (or more) until the whole Internet is secured (if ever) but there is light at the end of the tunnel. 0 TrackBacksListed below are links to blogs that reference this entry: .edu getting secured with DNSSEC . TrackBack URL for this entry: https://swarm.jupitermedia.com/mt-tb.cgi/8857 1 CommentsLeave a comment |
||
Sorry to disagree with some of the rosy comments concerning DNSSEC here.
In short DNSSEC is garbage. The encryption is easy to break. It's a major cost to business to be DNSSEC enabled.
You also run the risk of having your web sites disconnected from the net. This problem was identified by Dr. Bernstein and labeled DNSSEC suicide.
Nor does DNSSEC solve the Kaminsky security issue - which is not related to the DNS but to the UDP transport. DNSSEC leaves the UDP security issue wide open.
The solution that fixes the UDP problems via is DNS is DNSCurve. http://bit.ly/pJVq4
Folks DNSSEC is a joke - http://bit.ly/EzoYt - we can not afford to adopt it commercially. Push for DNSCurve.