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
After a KeyRefresh/Auxiliary protocol we get a keyshare with the same verifying key, which makes it easy to confuse with an obsolete keyshare (and, for example, start a signing protocol with one). We need some kind of a publicly accessible "refresh ID" which will be updated after each refresh. Can the rho value generated during the protocol be used for that? Or we can just hash PublicAux.
The text was updated successfully, but these errors were encountered:
After a KeyRefresh/Auxiliary protocol we get a keyshare with the same verifying key, which makes it easy to confuse with an obsolete keyshare (and, for example, start a signing protocol with one). We need some kind of a publicly accessible "refresh ID" which will be updated after each refresh. Can the
rho
value generated during the protocol be used for that? Or we can just hashPublicAux
.The text was updated successfully, but these errors were encountered: