@BRIAN_____ @tqbf It wasn't us who proposed this "there can be only one" CFRG process.
-
-
@bascule@brian_____@tqbf a lot of folks seemed to define obstructing as "Proposing something other than 25519" -
@marshray@BRIAN_____@tqbf do you think it makes sense for Microsoft to be pushing short Weierstrass curves? -
@bascule@brian_____@tqbf I don't know. I think the quality of specification and library implementation matters far more. -
@marshray@BRIAN_____@tqbf Weierstrass is harder to implement and has more wiggle room for fuck-ups. Yet that's what Microsoft pushed... -
@marshray@BRIAN_____@tqbf the rest of the ECC world had mostly moved onto Montgomery/Edwards by that point... -
@marshray@BRIAN_____@tqbf Microsoft eventually came around and got on the Edwards bandwagon but had... weird ideas about rigidity
End of conversation
New conversation -
-
-
@marshray@BRIAN_____@tqbf most of Microsoft's proposals seemed... kind of insane? Who wants to be implementing short Weierstrass in 2014? -
@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 -
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.