keybase / keybase/client

[Security Feature] Client button to disable web setting changes.

Open
#12,874 4 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

  1. Email change
  2. Password change
  3. Notification settings change
  4. Account deletion
  5. Individual device revocation ("Reset all keys" for the web login)

Can all be done via Keybase Client.......

So therefore:

Request

Add a button in the client that allows me to nuke the above 5 features from web.

User story

  1. User sets up a device and logs in to the device.
  2. User generates paper key and stores in safe place.
  3. User saves username and password in password manager.
  4. User is confident they will never get locked out.
  5. User clicks a button (and confirms by writing something).
  6. Client signs a message with the device key telling the keybase server to not allow this account to change the above settings from the web UI.

This will prevent an attacker from destroying accounts or tricking people who don't pay attention into letting them back into a team and stealing private info etc.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by tracing the Keybase client and server handling for web email, password, notification, deletion, and device-revocation changes, then determine how a device-key-signed account policy would be represented and enforced. Done means the client control and confirmation flow work for all five settings and the server rejects web changes when enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, react, react-native
Domain
authentication, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.