-
## Why
As we are currently implementing the revision number 2 of the OTRv4 specification, we need to include a consistent way of using user profiles and prekey profiles.
## Reference
Please, …
-
## Why
As we are currently implementing the revision number 2 of the OTRv4 specification, we need to correctly implement heartbeat messages.
## Reference
The current implementation seems not …
-
## Why
As we are currently implementing the revision number 2 of the OTRv4 specification, we need to include a consistent way of deleting secret information.
## Reference
Please, refer to the…
-
## 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…
-
Original message:
> There are a lot of missing links to the OTRv4 specification that
> should state exactly to which section it is referring.
-
## Why
As we are currently implementing the revision number 2 of the OTRv4 specification, we need to include a consistent way of safely using points.
## Reference
Please, refer to the "Genera…
-
This is the specification we refer to in section "Publishing prekey messages" and "Receiving prekey messages" in OTRv4.
The spec should include how many prekeys may be returned.
-
This section assumes that A1 is the public key, but the function must be generalized to work with any of the keys (while using constant-time conditional copies and other techniques to avoid side chann…
-
If my interpretation is correct, RSig should allow a third party, e.g. Carol, to forge conversations between Alice and Bob, with only their client profiles accessible.
It seems Carol can:
0. Ext…
-
In section "Create a User Profile Signature", step 2 of the block-quote section, it specifies that `len(c)` is appended. Consider making explicit here or in the section above that `len(c)` is to be pe…