-
Notifications
You must be signed in to change notification settings - Fork 0
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
Improve Keybase Integration #3
Labels
Comments
As of c28127d the browser action has a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're currently using Keybase to get all the users that have "proof" of ownership of the domain we're loading a script from, ask the user whether they'd like to trust them and then grab all the 'trusted' public keys and use them to verify the scripts are signed.
Right now we just show the user the Keybase user's username when asking whether or not they want to trust the user. We should make use of Keybase's vast amount of "proof" that a Keybase user is in fact a person that we trust by showing the end user some of their details.
We should also pin 'trusted' users by more than just their username as we don't take into account identity proofs being revoked, potentially indicating that the Keybase account is no longer under the trusted person's control.
The text was updated successfully, but these errors were encountered: