-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Offline conversation not continuing #55
Comments
If we go for this option: Every time you send offline messages to a participant, you start a new DAKE; then this worries me from an specification level. This ratchet will only be encrypted not with new ephemeral material but with the "fake sending chain key" (We decided to derive a sending ratchet key from the Mixed shared secret, and to make the first root key to 0.). There will be no subsequent ratchets, so it will only be encrypted with that. |
Hmmmmmmm. So yeah, from my side, the optimal would be this:
This does imply that the ratchets should be kept even when people are going offline. Maybe even after restarting the program? Does this answer the questions in this issue? |
Already happening.
Yes. And then it is actually ratcheting.
Yes. But I'm not sure how possible is this. We will gave to write the state of the ratchet somewhere? |
Yeah, that's what worries me a little. But it seems like the right way to give a good user experience. |
Yeah... let's do that |
More discussion for this one before implementing anything. |
Right now the offline conversation is working this way:
Alice sends data messages to offline Bob and he successfully receives them.
Bob starts a new DAKE and sends data messages to offline Alice and Alice successfully receives them.
However, it should be possible to do this:
(All in the same DAKE)
Alice sends data messages to offline Bob and he successfully receives them; Bob, when coming online, in the same conversation, sends data messages to offline Alice and she successfully receives them.
Right now, this is impossible to do, because every time that Alice logs in, she does not keep the previous state machine, and if she receives data messages in the same dake, they will be in
?OTR Error: ERROR_2: OTRNG_ERR_MSG_NOT_PRIVATE_STATE
.How shall we handle this?
The text was updated successfully, but these errors were encountered: