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
Currently all messages are just encrypted and decrypted using the latest keypair of the respective channel. This implementation is not suitable if keypairs should be dynamic and easy to change. Future server implementations will at least enforce clients to reference a recent channel update message as dependency.
The text was updated successfully, but these errors were encountered:
While reviewing a pull request I noticed that the Skynet app always takes the latest keypair for the respective channel and does not even respect MessageFlags.Loopback. Although this will not lead to crashes or corrupted messages, it violates the protocol rules and will not be compatible with other client implementations.
Currently all messages are just encrypted and decrypted using the latest keypair of the respective channel. This implementation is not suitable if keypairs should be dynamic and easy to change. Future server implementations will at least enforce clients to reference a recent channel update message as dependency.
The text was updated successfully, but these errors were encountered: