-
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 …
-
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…
-
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…
-
Such as Ricochet.
-
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 message:
> * What happens if you receive two prekey messages with user profiles
> signed with different long-term keys?
>
> What happens if you locally have two user profiles? This can…
-
Hi all, I've got several questions regarding the Client Profile sections and the use of client profiles. Some of these are intended for confirmation of correct understanding.
1. I should validate t…
-
- [x] On "Non-interactive DAKE Overview" section, state that when Alice requests prekey messages from the untrusted server, she specifically asks for prekey messages for Bob.
- [x] On "Non-interactiv…
-
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…
-
The OTRv2 and v3 is doing version according to the query message `?OTRv3?`, we should consider downgrade attack if MITM has capability to change this header.
Or, once we have otr4, we should also con…