Skip to content

v0.5.4

  • v0.5.4
  • c185c83

  • Verified

    This commit was signed with the committer’s verified signature.
    nel349 Norman Lopez
    SSH Key Fingerprint: QEpslh6MGdTIJXlmmk6XIEsEnsgHXNFm2j0qMgLhJNw
    Verified
    Learn about vigilant mode

  • Choose a tag to compare

    View all tags
v0.5.4: fix(serve): signData signs a prefixed message; release 0.5.4
  • v0.5.4
  • c185c83

  • Choose a tag to compare

    View all tags

  • Verified

    This commit was signed with the committer’s verified signature.
    nel349 Norman Lopez
    SSH Key Fingerprint: QEpslh6MGdTIJXlmmk6XIEsEnsgHXNFm2j0qMgLhJNw
    Verified
    Learn about vigilant mode
@nel349 nel349 tagged this 11 Oct 04:39 
The key that signs for signData also signs the wallet's unshielded spends,
over a transaction's signature data. signData signed the dApp's bytes as
given, so a dApp could send a transaction's signature data as its message
and get back a valid spend signature. It now signs
"midnight_signed_message:<byte length>:" followed by the data, as the
connector spec requires a prefix.

BREAKING CHANGE: verifiers must check signData signatures over the
prefixed message.

Claude-Session: https://claude.ai/code/session_01XQWkwdzqCkXVWeFrvJZ8RQ
Assets 2
Loading