Skip to content
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

Remove vg-request-with-auth from IMAP after processing #6208

Open
link2xt opened this issue Nov 14, 2024 · 1 comment · May be fixed by #6354
Open

Remove vg-request-with-auth from IMAP after processing #6208

link2xt opened this issue Nov 14, 2024 · 1 comment · May be fixed by #6354
Assignees

Comments

@link2xt
Copy link
Collaborator

link2xt commented Nov 14, 2024

Alice currently does not remove the message from IMAP for some reason stated in the comment:

Ok(HandshakeMessage::Ignore) // "Done" would delete the message and break multi-device (the key from Autocrypt-header is needed)

In multi-device case this may result in situation when Bob join the group, then leaves it, then second Alice device comes online and processes vg-request-with-auth again and adds Bob back.

I don't see why Autocrypt header is needed by the second device, Alice should see self-sent "member added" message and take gossiped Bob's key from there.

This is a follow-up to #5356

@iequidoo
Copy link
Collaborator

I don't see why Autocrypt header is needed by the second device

Probably because it's a common code for the "verified groups" and "verified contacts" setup protocols. Yes, it seems that vg-request-with-auth may be safely IMAP-removed, but we should make sure that gossiping happens even in case of two-member groups and add a test for that.

@iequidoo iequidoo self-assigned this Dec 18, 2024
iequidoo added a commit that referenced this issue Dec 21, 2024
In multi-device case `vg-request-with-auth` left on IMAP may result in situation when Bob joins the
group, then leaves it, then second Alice device comes online and processes `vg-request-with-auth`
again and adds Bob back. So we should IMAP-delete `vg-request-with-auth`. Another device will know
the Bob's key from Autocrypt-Gossip. But also we should make sure that `vg-member-added` is sent
before that. For this, add a new `imap.target_min_smtp_id` column and only move or delete emails
when `smtp.id` reaches the `imap.target_min_smtp_id` value.
iequidoo added a commit that referenced this issue Dec 22, 2024
In multi-device case `vg-request-with-auth` left on IMAP may result in situation when Bob joins the
group, then leaves it, then second Alice device comes online and processes `vg-request-with-auth`
again and adds Bob back. So we should IMAP-delete `vg-request-with-auth`. Another device will know
the Bob's key from Autocrypt-Gossip. But also we should make sure that `vg-member-added` is sent
before that. For this, add a new `imap.target_min_smtp_id` column and only move or delete emails
when `smtp.id` reaches the `imap.target_min_smtp_id` value.
iequidoo added a commit that referenced this issue Dec 22, 2024
In multi-device case `vg-request-with-auth` left on IMAP may result in situation when Bob joins the
group, then leaves it, then second Alice device comes online and processes `vg-request-with-auth`
again and adds Bob back. So we should IMAP-delete `vg-request-with-auth`. Another device will know
the Bob's key from Autocrypt-Gossip. But also we should make sure that `vg-member-added` is sent
before that. For this, add a new `imap.target_min_smtp_id` column and only move or delete emails
when `smtp.id` reaches the `imap.target_min_smtp_id` value.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants