@bascule @WatsonLadd Maybe also drop the 224-bit security level?
-
-
Replying to @DLitz1 reply 0 retweets 0 likes
-
-
Replying to @DLitz
@WatsonLadd@bascule Honestly, we're never going to have widespread, correct implementations unless we stop having dozens of silly options.1 reply 0 retweets 0 likes -
Replying to @DLitz
@DLitz@WatsonLadd we’re never going to get anywhere if we keep arguing about what curves to use…2 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@WatsonLadd True, but it's also pointless theater if enough implementations end up insecure, even if on paper it's "high security".1 reply 0 retweets 0 likes -
Replying to @DLitz
@DLitz@WatsonLadd I don't see how that comment has anything to do with a conversation on curve selection1 reply 0 retweets 0 likes -
Replying to @bascule
Darsey Litzenberger Retweeted Darsey Litzenberger
@bascule@WatsonLadd https://twitter.com/DLitz/status/530604729965899776 … https://twitter.com/DLitz/status/530606180863705089 …https://twitter.com/DLitz/status/530607321345314816 …Darsey Litzenberger added,
1 reply 0 retweets 0 likes -
Replying to @DLitz
@DLitz@WatsonLadd so your alternative is one curve to rule them all and a single ciphersuite? What happens when something breaks?2 replies 0 retweets 0 likes -
Replying to @bascule
@bascule@WatsonLadd One per generation, and in return you get simpler implementations & shorter upgrade cycles.1 reply 0 retweets 0 likes
@DLitz @WatsonLadd I think that @trevp__'s Noise builds in support for multiple curves in an unobtrusive way: https://github.com/trevp/noise/wiki/Ciphersuites …
-
-
Replying to @bascule
@bascule@WatsonLadd@trevp__ Yeah, basically something like that.0 replies 0 retweets 0 likesThanks. 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.