5 ms·
Or via HTTP. Why bother with DNS? Just put them at /certs.txt and serve them over HTTP. It would be equally as secure as serving them over DNS, that is not at a
by IgorPartola 12y ago
Or via HTTP. Why bother with DNS? Just put them at /certs.txt and serve them over HTTP. It would be equally as secure as serving them over DNS, that is not at all.
- toomuchtodo 12y agoHTTP is insecure and could be MITM. And HTTPS is no good as you don't know if you can trust the cert, as you couldn't get the fingerprints before connecting. DNSSEC is secure.
- IgorPartola 12y agoYet, DNSSEC introduces a huge number of other problems like giving government agents even more control over the Internet. I was strongly in the DNSSEC camp until doing more research into it. I'd summon @tptacek for this discussion, but I think you've actually participated in a few of those already with him.