jocluteseh

4 ms·

1.
by jocluteseh 12y ago
> You are assuming that your client OS/browser DNS resolvers have the pre-shared trust anchors for whichever root zone. That's kind of a big assumption. First: There are two arguments to be had. One is the server side, and one
2.
by jocluteseh 12y ago
> Fair enough.. but if you're talking to a MITM anyway, would you agree that it's game over? Don't think: 1/10,000 chance. Think: 1/1,000,000,000,000,000,000,000 chance. You are much more likely to die by getting
3.
by jocluteseh 12y ago
I'll try to post a comment, but my IP address may be rate limited -- I keep getting "You are posting too fast" errors. In any case, you've made my case for me much better than I could have made it myself. The problem wi
4.
by jocluteseh 12y ago
Done... enjoy... or not, but just make sure the beer is cold. https://gist.github.com/anonymous/3f36dfeb3297e184417b#file-...
5.
by jocluteseh 12y ago
1.a.1 I think this is your main fault. You are assuming that end-to-end encrypted message content is equatable to 'insecure' SMTP. The clear text or encrypted content of an email message has nothing to do with validating that a
6.
by jocluteseh 12y ago
Fixed formatting a little here: http://shortText.com/6308c7af
7.
by jocluteseh 12y ago
1. Why? An unqualified blanket statement does not prove anything. SPF, DKIM, DMARC provide strong cryptographical ties to a specific, real, and verified account holder. DNSSEC provides domain level certification. So, with all four items,
8.
In Defense of DNSSEC(shorttext.com)
15 points by jocluteseh 12y ago|64 comments