Document the potential for message replays and possible mitigations
This commit is contained in:
parent
5a98012c0d
commit
8c4a11a92d
1 changed files with 10 additions and 0 deletions
|
@ -274,6 +274,16 @@ bytes preceding the signature.
|
||||||
Limitations
|
Limitations
|
||||||
-----------
|
-----------
|
||||||
|
|
||||||
|
Message Replays
|
||||||
|
---------------
|
||||||
|
|
||||||
|
A message can be decrypted successfully multiple times. This means that a MITM
|
||||||
|
server can send multiple copies of a message and they will successfully decrypt.
|
||||||
|
|
||||||
|
To mitigate this it is recomendend that applications track the message indicies
|
||||||
|
they have recieved and that they reject messages with indicies that they've
|
||||||
|
already decrypted.
|
||||||
|
|
||||||
Lack of Transcript Consistency
|
Lack of Transcript Consistency
|
||||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue