@BRIAN_____ @tqbf this captures the "anyone who proposes anything other than 25519 is being unhelpful" argument nicely
-
-
Replying to @marshray
@marshray@BRIAN_____@tqbf Microsoft may have had good intentions but to an outsider it really feels like they were obstructing the CFRG2 replies 0 retweets 2 likes -
Replying to @bascule
@bascule@brian_____@tqbf a lot of folks seemed to define obstructing as "Proposing something other than 25519"1 reply 0 retweets 0 likes -
Replying to @marshray
@marshray@BRIAN_____@tqbf do you think it makes sense for Microsoft to be pushing short Weierstrass curves?1 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@brian_____@tqbf I don't know. I think the quality of specification and library implementation matters far more.2 replies 0 retweets 0 likes -
Replying to @marshray
@marshray@bascule@BRIAN_____@tqbf the problem being: Curve25519 is *really* the best option. nothing to tune there.2 replies 0 retweets 0 likes -
Replying to @a_z_e_t
@a_z_e_t@marshray@BRIAN_____@tqbf yeah, the inevitable conclusion was: Microsoft's curve generator produces Curve255191 reply 0 retweets 0 likes -
Replying to @bascule
@bascule@marshray@BRIAN_____@tqbf yes. I don't think they were trying to obstruct anything though. the whole RG is obstructing itself. :)1 reply 0 retweets 0 likes -
Replying to @a_z_e_t
@a_z_e_t@bascule@BRIAN_____@tqbf If it's clear nobody could predict the outcome of the process, does that preserve the NUMS property? :-)2 replies 0 retweets 1 like -
Replying to @marshray
@marshray@a_z_e_t@bascule@BRIAN_____ i would also argue secp256k1 2nd most used curve, 10m+ pubkeys published, yet nuked in NSS in 2006.2 replies 0 retweets 0 likes
@_miw @marshray @a_z_e_t @BRIAN_____ Koblitz curves, used by Bitcoin and nothing else... Satoshi chose a weird curve, nothing to see move on
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.