Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

[e2e] Web-of-trust type of verification process for verifying keys in a group. #662

Closed
arthurlutz opened this issue May 5, 2017 · 4 comments

Comments

@arthurlutz
Copy link

Related to matrix-org/matrix-spec-proposals#3656 a more "web-of-trust" could be an option too : verify/trust all devices trusted by user X or by all existing users in the room with a display of number of users that trust a given key.

@arthurlutz arthurlutz changed the title [e2e[ Web-of-trust type of verification process for verifying keys in a group. [e2e] Web-of-trust type of verification process for verifying keys in a group. May 5, 2017
@TheLastProject
Copy link

I don't quite like this idea. It simplifies mapping out who someone interacts with by seeing if the keys are trusted. It'll leak private metadata for very little possible benefit (most people don't correctly trust keys in the first place, even more technical users, I have never been able to trust the web of trust for GPG keys either).

@uhoreg
Copy link
Member

uhoreg commented Sep 27, 2019

@hugecheese
Copy link

@TheLastProject Is there any other solution to scaling verification?

N^2 verifications makes any E2EE room with more than 5 members basically unusable. There any many circumstances when you wouldn't want everyone to verify everyone.

Web-of-trust is fairly reliable in workplace/small-community environments. It only makes sense that I would be able to trust my boss's verifications. He's running the room after all, it's his ass if the E2EE is voided by improper verification.

@Avamander
Copy link

The very least this approach could provide a way to have a little more trust in fellow room members than them being totally unverified(!1! red text color) like right now.

@t3chguy t3chguy transferred this issue from element-hq/element-web Sep 27, 2022
@element-hq element-hq locked and limited conversation to collaborators Sep 27, 2022
@t3chguy t3chguy converted this issue into discussion #663 Sep 27, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

7 participants