@BRIAN_____ @tqbf It wasn't us who proposed this "there can be only one" CFRG process.
@marshray @BRIAN_____ @tqbf after a lot of teeth pulling and backpeddling, we wound up with rigid curve generation that generates Curve25519
-
-
@bascule@brian_____@tqbf which kind of raises questions about rigidity in a committee process (not security tho) -
@marshray@BRIAN_____@tqbf I spoke out against rigidity: https://www.ietf.org/mail-archive/web/cfrg/current/msg05767.html …
End of conversation
New conversation -
-
-
@bascule@marshray@BRIAN_____@tqbf it gets more ridiculous by the day. I opt for TLS-WG just adopting the draft and move on. -
@bascule@marshray@BRIAN_____@tqbf and as people have pointed out; signature schemes have not even been discussed yet. :/ -
@a_z_e_t@marshray@BRIAN_____@tqbf I just started a thread! :o -
@bascule@marshray@BRIAN_____@tqbf oh, just saw. been over @ TLS-WG stating TLS 1.0 & NSA drafts should be abandoned as well. :) -
@bascule@marshray@BRIAN_____@tqbf (the extended random and opaque prf stuff which will only cause implementation issues AFAICT)
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.