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
To make sure that no replay attacks on encrypted forwarded requests from a backup to the primary can be performed, each node to node channel should keep track of the sender and receiver nonces (i.e. GCM IV) to check for continuity of messages sent.
This new mechanism should be resilient to loss of messages over the channel and reconnections. A unit test will probably be the best way to verify this behaviour.
The text was updated successfully, but these errors were encountered:
To make sure that no replay attacks on encrypted forwarded requests from a backup to the primary can be performed, each node to node channel should keep track of the sender and receiver nonces (i.e. GCM IV) to check for continuity of messages sent.
This new mechanism should be resilient to loss of messages over the channel and reconnections. A unit test will probably be the best way to verify this behaviour.
The text was updated successfully, but these errors were encountered: