Yes, with improper/poor implementation your might face the problems. DNSSEC uses public key cryptography and you need to maintain it. Administrating DNS is a fun stuff when you are enabling DNSSEC in your production (you need to know more). Come on, you know should read these RFCs 4033, 4034, 4035 and 5011. If anyone got doubt about DNSSEC, we can discuss about it. Root server will enable DNSSEC in production by July this year and for .my in Q4 this year. UDPPoke, Poke, Poker, TCPPoke... great.
rgds Amir Haris On Sat, Apr 10, 2010 at 8:03 PM, BRIAN RITCHIE <[email protected]>wrote: > Thanks for this. Will check it out. > > On Sat, Apr 10, 2010 at 3:00 PM, Muhammad Najmi Ahmad Zabidi < > [email protected]> wrote: > >> http://cr.yp.to/talks/2009.08.10/slides.pdf >> >> DJB, the author of Qmail >> >> -- >> You received this message because you are subscribed to the Google Groups >> "MySecurity" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<mysecurity%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/mysecurity?hl=en. >> >> > > _______________________________________________ > Owasp-Malaysia mailing list > [email protected] > https://lists.owasp.org/mailman/listinfo/owasp-malaysia > > OWASP Malaysia Wiki > http://www.owasp.org/index.php/Malaysia > > OWASP Malaysia Wiki Facebook > http://www.facebook.com/pages/OWASP-Malaysia-Local-Chapter/295989208420 >
_______________________________________________ Owasp-Malaysia mailing list [email protected] https://lists.owasp.org/mailman/listinfo/owasp-malaysia OWASP Malaysia Wiki http://www.owasp.org/index.php/Malaysia OWASP Malaysia Wiki Facebook http://www.facebook.com/pages/OWASP-Malaysia-Local-Chapter/295989208420
