@BRIAN_____ @tqbf It wasn't us who proposed this "there can be only one" CFRG process.
@a_z_e_t @marshray @BRIAN_____ @tqbf yeah, the inevitable conclusion was: Microsoft's curve generator produces Curve25519
-
-
@bascule@marshray@BRIAN_____@tqbf yes. I don't think they were trying to obstruct anything though. the whole RG is obstructing itself. :) -
@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? :-) -
@marshray@a_z_e_t@bascule@BRIAN_____ monoculture of curve25519 & new code is troublesome. Impl. BP384r1 in NSS uncovered field arith bugs -
@_miw@marshray@a_z_e_t@BRIAN_____ fuck Brainpool -
@bascule@_miw@marshray@BRIAN_____ i'm sure it has it's use cases. i'd prefer NIST crvs these days over brainpool. it's in TLS anyway. :/ -
@a_z_e_t@bascule@marshray@BRIAN_____ lol like you have a choice with curves in TLS! Where's my EdDSA certs to match... -
@_miw@a_z_e_t@marshray@BRIAN_____ I hope they're coming soon
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.