@NullDereference @veorq @bascule yea, very true. it got to a point where the whole mailing list just seemed destructive.
@NullDereference @a_z_e_t @veorq what do you mean? We've gotten as far as Curve25519 and Ed448-Goldilocks with Montgomery-x for D-H...
-
-
-
@NullDereference@bascule@veorq who do you think would have realistically doen that faster? polls didn't stall as much as other discussions -
-
@NullDereference@bascule@veorq BTW. while I like the idea I don't think TLS 1.3 should have a MUST NOT for <1.2, the BCP says that already -
-
@NullDereference@bascule@veorq but what does it mean? a 1.3 server can't negotiate 1.1 at all? lock clients out on a certain lib version? -
-
@NullDereference@bascule@veorq that's the bad crypto vs. no crypto fallback discussion again, right? - 1 more reply
New conversation -
-
-
@NullDereference@a_z_e_t@veorq that alone seems like a pretty major accomplishment, and ChaCha20+Poly1305 is happening too -
@bascule@NullDereference@veorq chacha/poly is currently up in TLS-WG for adoption calls. -
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.