Skip to content

test key leakage via signature when varying public key

  • As described on https://github.com/MystenLabs/ed25519-unsafe-libs, a private key can be leaked when an invalid public key is used to create an ed25519 signature
  • The fix for this is generally to require the private key and then derive the public key from the private
  • This does not work for threshold signing as the cosigners do not have a complete private key, only their respective shares
  • In testing however it does not appear that threshold signing is susceptible to this, the leaked value in this case is the ephemeral public key
  • I also bumped the go version and fixed the linting while I was here

Merge request reports

Loading