You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also, a malicious user could hang out and submit a new CSR for any name anyone requests.
We can choose a winning CSR randomly when more than one CSR requests the same name. But if someone floods CSRs with new keys that won't matter since probability will be on their side.
Related to #1892. How can we prevent this? Perhaps, if pubKeys are added to a chain of trust (e.g. via local-first-auth)?
The text was updated successfully, but these errors were encountered: