Skip to content

MSC3834: Opportunistic user key pinning (TOFU)#3834

Open
duxovni wants to merge 3 commits intomainfrom
fayed/tofu
Open

MSC3834: Opportunistic user key pinning (TOFU)#3834
duxovni wants to merge 3 commits intomainfrom
fayed/tofu

Conversation

@duxovni
Copy link

@duxovni duxovni commented Jun 14, 2022

@duxovni duxovni changed the title MSC: Opportunistic user key pinning (TOFU) MSC3834: Opportunistic user key pinning (TOFU) Jun 14, 2022
@turt2live turt2live added e2e proposal A matrix spec change proposal kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. labels Jun 14, 2022
@maralorn
Copy link

This is great! Thank you for pushing TOFU. I am though not sure that it’s acceptable UI to have this enabled by default. I suggest that clients targeting a large user base should only activate the warnings if the user has somehow demonstrated that they understand key signing, by either manually verifying a key or enabling an option in the settings. One could even consider a setting where users manually need to activate TOFU per user.

I think showing users who don‘t understand E2E warnings they don‘t understand (like Signal does) desensitizes them for security warnings and is bad UX.

I have already voiced my opinion in element-hq/element-meta#1557 (which I know see you self assigned, so I will stop here.)

Thanks for taking this on!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

e2e kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants