-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Share device verification/blocking status between our own devices #2537
Comments
Could you use the existing message e2e encryption method and just send a encrypted file containing a \n separated list of trusted keys? That way you don't break the message protocol and you get the e2e protection assuming you've verified at least your own two keys? |
element-hq/element-meta#647 is about sharing keys for chat history, but has the concept of asking another user/device for keys. "Matthew has added a new device 'iPad' and is requesting room history since Sept 18th. Do you want to share history?" ref For this issue what about a message to your older devices when you add a new one: "You just logged in width a new device, do you want to share encryption keys for your history with this new device?" And in return on the new device: "On other devices you have verified the keys of some contacts, would you like to trust the same ones on this device?" |
Just discussed this IRL with @richvdh; we kicked around the idea of just storing the verification state in a megolm room rather than finding another way to share encrypted JSON between our devices. We'd want to encrypt the verification data as well as sign it from a privacy perspective. Conclusion was that this is really a refinement of improving the verification UX and we should come back to it once focusing on improving verification. |
Verification process has been improved, but but there's still no synchronization of verified devices. |
We now partially have this on the verification side, with cross-signing. But we don't share blocking status yet. |
We now share blocked user status between devices so I will close this issue for now. If the issue is about another type of blocking, please update with more details and re-open. |
This issue isn't about the ignore user feature. It was about the blacklist feature which allowed you to stop sending encrypted messages to specific devices. That feature no longer exists but maybe will come back in the future #11751. |
We could use the account data for this, but we'd need to do some signing to stop it being forged
The text was updated successfully, but these errors were encountered: