Now do DNSCrypt.https://twitter.com/grittygrease/status/1044195562722144257 …
-
-
Replying to @CyberShambles
We do DoT and DoH, is that not enough? DNSCrypt was unfortunately never submitted to the IETF for standardization.
4 replies 0 retweets 0 likes -
Replying to @grittygrease @CyberShambles
It was never submitted because I feel like a submission by a random individual has zero chance to be considered. All DNS related proposals appear to always be backed by (a handful) companies, people who can afford going to expensive conferences to defend their proposal.
2 replies 3 retweets 2 likes -
Wait, am I expected to travel and defend XChaCha on my own dime in order to get it approved? D:
2 replies 0 retweets 0 likes -
It helps, but it’s definitely not a prerequisite. RFCs have been published by people who have never attended in person.
@goldbe has a good overview of how to get one done as an outsider: https://irtf.org/anrw/2018/anrwWelcome.pdf …. Rule #1: find an IETF native coauthor.1 reply 1 retweet 6 likes -
Replying to @grittygrease @CiPHPerCoder and
Thanks a lot, Nick. Now to find an IETF native coauthor…
1 reply 0 retweets 3 likes -
Replying to @jedisct1 @grittygrease and
I would help if you need it. Worked on a few drafts and published RFCs/BCPs
1 reply 0 retweets 2 likes -
Awesome! I'm using Github to coordinate the efforts:https://github.com/bikeshedders/xchacha-rfc …
1 reply 0 retweets 1 like -
Replying to @CiPHPerCoder @jedisct1 and
but why extended nonces? that issue is solved with 1.3
2 replies 0 retweets 0 likes
Because a stream cipher has other uses than TLS.
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.