ECDAA (part of WebAuthn) seems incredibly dangerously designed: https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-ecdaa-algorithm-v2.0-id-20180227.html#ecdaa-sign … + https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-ecdaa-algorithm-v2.0-id-20180227.html#encoding-ecpoint-values-as-byte-strings-ecpointtob … - Non-deterministic nonces - No point compression (hello invalid curve attacks) How the hell did this slip past cryptographers' radars?
-
Show this thread
Replying to @CiPHPerCoder
Hey Scott. I will pass your feedback to TWG *) Keep in mind that till now no one had implemented ECDAA so we have time to fix it *)
0 replies
1 retweet
8 likes
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.