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

Can't verify user when option to send keys to verified devices only is selected #532

Open
BillCarsonFr opened this issue Aug 3, 2022 · 3 comments
Labels
A-E2EE-SAS-Verification O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Team: Crypto

Comments

@BillCarsonFr
Copy link
Member

BillCarsonFr commented Aug 3, 2022

Steps to reproduce

  1. Go to Settings > Security
  2. Enable 'Encrypt to verified devices only'
  3. Go back to a DM with one of your contact, click on his profile
  4. Tap on verify.

Outcome

What did you expect?

That you initiate a verification process.

What happened instead?

It's failing because the recipient won't be able to decrypt the verification request
image

So it's quite annoying, I enabled 'Encrypt to verified devices only' and I have unverified users in a room. So you would think that verify them will fix the issue, but you can't

When using in-room messages and the room has encryption enabled, clients should ensure that encryption does not hinder the verification. For example, if the verification messages are encrypted, clients must ensure that all the recipient’s unverified devices receive the keys necessary to decrypt the messages, even if they would normally not be given the keys to decrypt messages in the room. Alternatively, verification messages may be sent unencrypted, though this is not encouraged.

Platform issues

@SimonBrandner SimonBrandner added S-Major Severely degrades major functionality or product features, with no satisfactory workaround O-Occasional Affects or can be seen by some users regularly or most users rarely T-Defect labels Aug 4, 2022
@MicahZoltu
Copy link

Why is this marked as occasional? I think it happens every time you get into this scenario.

@bmarty
Copy link
Member

bmarty commented Oct 6, 2022

Why is this marked as occasional? I think it happens every time you get into this scenario.

Probably because user has to enable 'Encrypt to verified devices only'.

@BillCarsonFr BillCarsonFr added this to the Crypto Q4 milestone Oct 14, 2022
@BrenBarn
Copy link

It's kind of terrible that you're unable to verify a user in the exact situation where you said you really really want to verify the user. . .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-E2EE-SAS-Verification O-Occasional Affects or can be seen by some users regularly or most users rarely S-Major Severely degrades major functionality or product features, with no satisfactory workaround T-Defect Team: Crypto
Projects
None yet
Development

No branches or pull requests

5 participants