Skip to content

Conversation

chappjc
Copy link
Member

@chappjc chappjc commented Mar 17, 2022

This is stage 1 of the signature message truncation fix plan outlined #1526.

In these commits, both client and server begin recognizing signatures of both the truncated messages or the message hash. Neither side begins signing the message hash. After this has been deployed to servers, the next stage (#1529) has the client begin creating signatures of the hashed messages.

@chappjc chappjc added this to the 0.4.2 milestone Mar 17, 2022
@chappjc chappjc requested a review from buck54321 March 17, 2022 19:21
@chappjc
Copy link
Member Author

chappjc commented Mar 17, 2022

Working when rebased on release-v0.4

chappjc added 3 commits March 17, 2022 15:01
Update the FundingCoin.Auth implementations to accept signatures
of a message that is either the truncated data (legacy clients) or a
client-specific hash of the message.

When we do the v0 purge (V0PURGE), the older buggy signatures
should be rejected.
@chappjc chappjc force-pushed the sign-verify-hash-server-only branch from 9ccbc2a to 5c4db49 Compare March 17, 2022 20:02
@chappjc chappjc changed the title server: start recognizing signatures of the hashed messages server: start recognizing signatures of the hashed messages (sig fix stage 1) Mar 17, 2022
@chappjc chappjc changed the title server: start recognizing signatures of the hashed messages (sig fix stage 1) start recognizing signatures of the hashed messages (sig fix stage 1) Mar 17, 2022
@chappjc chappjc merged commit 24b2038 into decred:master Mar 17, 2022
@chappjc chappjc deleted the sign-verify-hash-server-only branch March 17, 2022 21:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants