-
## Why
As we are currently implementing the revision number 2 of the OTRv4 specification, we need to include a consistent way of using both state machines.
## Reference
Please, refer to the "…
-
## Why
As we are currently implementing the revision number 2 of the OTRv4 specification, we need to include discarding flows to receiving the plaintext with whitespace tag.
## Reference
Plea…
-
## Why
As we are currently implementing the revision number 2 of the OTRv4 specification, we need to include a consistent way of queueing plaintext messages to an encrypted state.
## Reference
…
-
## Why
As we are currently implementing the revision number 2 of the OTRv4 specification, we need to include a consistent way of using OTR errors.
## Reference
Please, refer to the [OTR Error…
-
## Why
As we are currently implementing the revision number 2 of the OTRv4 specification, we need to include a consistent way of using the RSig function.
## Reference
Please, refer to the "Ri…
-
## Why
As we are currently implementing the revision number 2 of the OTRv4 specification, we need to include a consistent way of using Instance Tags.
## Reference
Please, refer to the "Instan…
-
## Why
As we are currently implementing the revision number 2 of the OTRv4 specification, we need to include an out-of-order double ratchet.
## Reference
Please, refer to "Interactive DAKE Ov…
-
## Why
As we are currently implementing the revision number 2 of the OTRv4 specification, we need to include a consistent way of using prekey messages.
## Reference
Please, refer to the "Prek…
-
## Why
As we are currently implementing the revision number 2 of the OTRv4 specification, we need to include a consistent way of attaching an encrypted message to the Non-Interactive-Auth message.
…
-
## Why
As we are currently implementing the revision number 2 of the OTRv4 specification, we need to include a consistent way of revealing MAC keys.
## Reference
Please, refer to the "Reveali…