Brainpool curves
bada55.cr.yp.to
bada55.cr.yp.to
Our experience is that Alice and Bob, when faced with a single procedure such as [BADA55-VPR's] (or [Brainpool's]), find it extremely difficult to envision the entire space of possible procedures (they typically see just a few dimensions of flexibility), and find it inconceivable that the space could have size as large as 2^20, never mind 2^30. (s5.3)
I find it pretty hilarious that someone found a way to weaponize the old quote "The wonderful thing about standards is that there are so many of them to choose from"
Any other standard using Brainpool curves?
key exchange:
https://tools.ietf.org/html/draft-irtf-cfrg-curves-09
signatures:
https://www.ietf.org/mail-archive/web/cfrg/current/msg07364....
https://en.wikipedia.org/wiki/Comparison_of_TLS_implementati...
In the RFC version, it will regenerate B until it is square, then do the other security checks.
That's unfortunate, but the generated curve should still satisfy all the requirements. There is little room for this to have an actual security impact. You would need an unknown attack that the original specification did not guard against, but randomly happened to avoid by its choice of seeding for the RFC method to be worse.