keybase / keybase/client

Grant limited access to some features/teams on some devices

Open
#18,573 1 comment 0 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

What I did

I logged in to Keybase on a device that I use frequently but is owned by someone else.

What happened

I don't see anyway to permission a device with anything other than "root" access to my Keybase data.

What I expected to happen

I hoped Keybase would let me grant a device limited access to my Keybase account. Specifically, so that I could use Keybase on the device to chat and access specific teams, but not to be able to access other teams, wallet, etc.

Thoughts

Possibly this will be addressed by having multiple accounts, and by #8586, but this is about retaining a single persona, a single identity, and instead providing a distinction between what teams should be accessible on what devices.

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

Start by reviewing this issue alongside the related multiple-accounts discussion in #8586. Define how one identity could grant a device access to chat and selected teams while excluding other teams, wallet data, and the rest of the account; done means those boundaries are enforceable on the target device.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authorization, mobile-dev, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.