-
Notifications
You must be signed in to change notification settings - Fork 23
Withdraw messages can be replayed #12
Comments
According to Matt's input we can bind additional parameters into the signature to prevent replay attacks, or enforce arbitrary logical conditions, see: At https://github.com/clearmatics/mobius/blob/master/contracts/Ring.sol#L164 the change would be something like, from:
to:
An equivalent change will need to be implemented in the |
in the paper we've changed this to the ring signature being formed over the intended recipient address (but this message is not included in the linking tag) -- it also means you can outsource the withdrawal transactions (ie, give it to someone else and include an incentive that pays them if the withdrawal transaction goes through or something) which will mitigate #34 as everyone then has some level of plausible deniability. I'll PR it when I get the chance! |
I've added some of my notes to #22 which covers different withdraw mechanisms, e.g. I might be overcomplicating it a bit though.
|
If a user submits a Withdraw message there is nothing preventing others from replaying the same message.
This is a concern if:
Until this problem is solved it would be possible for an attacker to monitor all rings and retransmit Withdraw messages with no cost of failure.
The text was updated successfully, but these errors were encountered: