-
As follow up to https://github.com/otrv4/otrv4/issues/147, if I understand your explanation correctly, this will cause problems in the following 2 use cases:
1. A secure conversation is initiated b…
-
## 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 …
-
Hello,
There are some problems for OTR:
- https://otr.cypherpunks.ca/
- http://otr.im/
- https://bugs.otr.im/explore
It is possible to redirect the old website (and all pages) to http://otr.i…
-
Original message:
> * Clarify the checks that the client should do upon receipt of the
> prekey messages. This should be included on the section and not only
> linked to certain part of the OTRv4…
-
I reported this before, but I want to revisit this as it was never fully discussed.
Current spec defines a single state machine covering both messaging and authentication. This is different in OTRv…
-
Original message:
> There are a lot of missing links to the OTRv4 specification that
> should state exactly to which section it is referring.
-
[Starting a conversation interactively](https://github.com/otrv4/otrv4/blob/master/otrv4.md#starting-a-conversation-interactively) describes how to initiate a secure session immediately given prior kn…
-
Original message:
> * Should DAKE prekey messages contain versions? I think no.. but there
> was not a clear outcome for this discussion:
> https://github.com/otrv4/otrv4-prekey-server/commit/2b5…
-
The prekey profile (https://github.com/otrv4/otrv4/issues/118) was not finished by the first version of the prekey server spec, so it was ignored.
This is about considering the prekey profile when …
-
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…