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

regression: Remove user from waiting queue when the key is set via updateGroupKey #33696

Open
wants to merge 1 commit into
base: release-7.0.0
Choose a base branch
from

Conversation

KevLehman
Copy link
Contributor

@KevLehman KevLehman commented Oct 21, 2024

Proposed changes (including videos or screenshots)

Issue(s)

https://rocketchat.atlassian.net/browse/E2EE2-89

Steps to test or reproduce

Further comments

This prevents the following edge case:

  • User A logs in, user forgot keys
  • User A creates a room, encrypted. As no keys, room stays in waiting queue state.
  • User A resets their E2E keys (cause he forgot)
  • User A logs in again, saves encryption keys.
  • Room previously created starts processing and user sets the group keys as expected.
  • User A invites User B to room
  • User B is waiting keys.
  • As user A reset their E2E keys, he's on the waitingQueue as well.
  • User A cannot provide keys to User B so he cannot send encrypted messages.

(regression since prior to v7, the user creating the room suggested and accepted a key via async key exchange)

Copy link
Contributor

dionisio-bot bot commented Oct 21, 2024

Looks like this PR is not ready to merge, because of the following issues:

  • This PR is missing the 'stat: QA assured' label

Please fix the issues and try again

If you have any trouble, please check the PR guidelines

Copy link

changeset-bot bot commented Oct 21, 2024

⚠️ No Changeset found

Latest commit: 72351d3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link
Contributor

PR Preview Action v1.4.8
🚀 Deployed preview to https://RocketChat.github.io/Rocket.Chat/pr-preview/pr-33696/
on branch gh-pages at 2024-10-21 19:53 UTC

Copy link

codecov bot commented Oct 21, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.97%. Comparing base (ce283bf) to head (72351d3).

Additional details and impacted files

Impacted file tree graph

@@              Coverage Diff               @@
##           release-7.0.0   #33696   +/-   ##
==============================================
  Coverage          74.97%   74.97%           
==============================================
  Files                480      480           
  Lines              21019    21019           
  Branches            5334     5334           
==============================================
  Hits               15760    15760           
  Misses              4630     4630           
  Partials             629      629           
Flag Coverage Δ
unit 74.97% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@KevLehman KevLehman added this to the 7.0 milestone Oct 21, 2024
@KevLehman KevLehman marked this pull request as ready for review October 21, 2024 20:19
@ggazzo
Copy link
Member

ggazzo commented Oct 22, 2024

tests ? 👀

@KevLehman
Copy link
Contributor Author

The thing with the tests is that this case shouldn't be possible. You should not be able to create rooms without your E2E keys setup in the first place (that's a diff issue).

So in reality there should be no way you hit this one. But I hit on candidate because the condition (not being able to create rooms without keys) is not working :/

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 this pull request may close these issues.

2 participants