MSC3834: Opportunistic user key pinning (TOFU)#3834
Open
Conversation
|
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!!! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rendered