@taoeffect CT should at least make the shady CAs more obvious
-
-
Replying to @bascule
@bascule If you’re replying to the John Oliver tweet, I removed it because CT isn’t as bad as loss of#NetNeutrality
.1 reply 0 retweets 0 likes -
Replying to @taoeffect
@taoeffect nah, talking about certificate transparency1 reply 0 retweets 0 likes -
Replying to @bascule
.
@bascule CT *might* catch *some* shady CAs. That doesn’t make it a good thing, as explained here: http://www.ietf.org/mail-archive/web/trans/current/msg00233.html …1 reply 0 retweets 0 likes -
Replying to @taoeffect
@taoeffect yeah, been following that thread. DANE would be a great approach if DNSSEC weren’t terrible1 reply 0 retweets 1 like -
Replying to @bascule
@bascule Somewhat similar to DANE is JWS: https://tools.ietf.org/html/draft-ietf-jose-json-web-signature-17 …@DNSChain supports DANE, and will support JWS or something similar.1 reply 1 retweet 1 like -
Replying to @taoeffect
@taoeffect@DNSChain been flollowing JWS too but it feels like some round hole square peg stuff IMO1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@DNSChain Reason for JWS-type thing is to make@okTurtles possible.1 reply 0 retweets 0 likes -
-
-
Replying to @taoeffect
@taoeffect it covers both cases, but the descriptions need to be updated0 replies 0 retweets 1 like
End of conversation
New conversation
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.