Skip to content

Conversation

@duxovni
Copy link
Contributor

@duxovni duxovni commented Aug 4, 2022

Checklist

  • Tests written for new code (and old code if feasible)
  • Linter and other CI checks pass
  • Sign-off given on the changes (see CONTRIBUTING.md)

Here's what your changelog entry will look like:

✨ Features

  • Always block sending keys to unverified devices of verified users (#2562). Contributed by @duxovni.

@duxovni duxovni requested a review from a team as a code owner August 4, 2022 02:09
Copy link
Member

@dbkr dbkr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good - is there a bug somewhere tracking this change / documenting the decision for doing it?

@duxovni
Copy link
Contributor Author

duxovni commented Aug 4, 2022

Not that I'm aware of, this was more the output of internal Crypto Team conversations. Thanks for the review!

@duxovni duxovni merged commit 43b4538 into develop Aug 4, 2022
@duxovni duxovni deleted the fayed/verified-user-unverified-device branch August 4, 2022 15:11
duxovni added a commit that referenced this pull request Aug 8, 2022
…sers (#2562)"

This will be rolled out again later with more accompanying UI
adjustments, including clearer error messages and possibly the option
to disable it per-room.
duxovni added a commit that referenced this pull request Aug 8, 2022
…sers (#2562)" (#2571)

This will be rolled out again later with more accompanying UI adjustments, including clearer error messages and possibly the option to disable it per-room.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants