-
The protocol modes, that can be found on this ADR: https://github.com/otrv4/otrv4/blob/master/architecture-decisions/0010-modes.md . We settle down for two modes:
1. OTRv4 only mode, and
2. OTRv…
-
Currently, there seems to be three memory leaks (that show up randomly on ci):
```
==10767== Use of uninitialised value of size 8
==10767== at 0x5149819: encodeblock (b64.c:89)
==10767== by 0x51…
-
## 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
A library should be sufficiently secure and functional in the ways it is written. TLV handling should follow that.
## Reference
As the TODO here included: ee751f0caad3a4cf90f92dd73c82…
-
This paragraph keeps coming as something that should be in the prekey server spec:
```
i. If the versions and the long-term keys used in the messages are the same, and they are
compatible with Al…
-
## Why
A library should be sufficiently consistent in the ways it is written.
## Reference
21st Century C, Chapter 8, "True and False", page 147.
## Discussion
When should be use bool.…
-
## 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.
-
Original TODO
> Check replay, key reused, attacker modifies prekey or format?
>- What if the server delivers all the prekey messages to an adversary
> - How does forward secrecy is compromised …