Hacker News new | past | comments | ask | show | jobs | submit login

DNSSEC is probably OK if all you use it for is within an organization for your own stuff (ie, with your corporate root CA, for your corporate domains only, where you control for and vouch for every node connected), and then using it to enhance other things like distributing SSH keys through SSHFP (again, totally internally, not internet facing).

But everything else said here I totally agree with - if you don't control the root, you don't control a whole lot of anything.

If you want something that hides the contents of DNS packets in transit, DNSCurve at least does that, and is relatively easy to deploy - the current best server appears to be the curvedns in the freebsd ports (updated to use libsodium, etc.): https://svnweb.freebsd.org/ports/head/dns/curvedns/




> if you don't control the root, you don't control a whole lot of anything.

What's of course valid for TLS too. Do you suggest people use HTTPS?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: