To clarify the Windows crypto fail: The problem isn't in signature validation. The problem is the *root store/cache*. CryptoAPI considers an (attacker-supplied) root CA to be in the trust store if its public key and serial match a cert in the root store, Ignoring curve params.
-
Show this thread
-
Replying to @marcan42
How difficult is it to exploit? Ie. how much processing power does it take to create the key pair with an identical public key? Or perhaos those are already for sale?
1 reply 0 retweets 1 like -
Replying to @MrG_A
It takes the same amount of time as to generate a key normally. So microseconds. Maybe milliseconds.
1 reply 0 retweets 2 likes -
Replying to @marcan42
Would you mind ELI5 or link to an article which isn't crap? To me it sounds a bit like bruteforcing a private key from a public one.
1 reply 0 retweets 0 likes
The public key is the curve base point times the private key. This is secure because multiplication in ECC is like a hash, it's not easily invertible. If you can change the base point, you just set the private key to 1 and the base point to whatever public key you want.
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.