@bascule looks like he's making a (valid?) rigidity argument. Unfortunately there's a meta-rigidity issue, which you're pointing out.
-
-
-
@mik235 they want to use a curve with a class of weak keys/potential twist security issues/implementation issues/ instead of Curve25519? NO -
@bascule sure, but maybe@hashbreaker knows of some other, far worse security issue that the rest of the world doesn't -
@mik235 that's the argument@hashbreaker makes about the NIST curves, lol
End of conversation
New conversation -
-
-
@bascule "embrace and extend" -
@postmodern_mod3 "we like Curve25519, but we want to change A to 358990 because we don't understand twist security"
End of conversation
New conversation -
-
-
@bascule I really can't stand people that fight good solutions just because it wasn't their idea. No good reason to not use Curve25519. -
.
@adamcaudill Benjamin Black is arguing nobody read his draft when he failed to read or account for@hashbreaker's response to his draft - 1 more reply
New conversation -
-
-
@bascule OTR in its C library is quite complex, but it does not work, 5mn break, repeat, and longer breaks sometimes.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.