`keybase team request-access` claims to hide team existence, but `keybase team create` reveals it
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
If I request access to a team that already exists, I get a privacy-preserving message:
~> keybase team request-access $existing_team
If "$existing_team" exists, an email has been sent to its admins, notifying of your request for access.
However, if I try to create the team, I can see whether it already exists:
~> keybase team create $existing_team
▶ ERROR team already exists (code 2619)
I'm not sure it's a bad thing to reveal the existence of teams, but these two things are not consistent :)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the privacy behavior of keybase team request-access and keybase team create for an existing team. The issue does not specify which behavior should change, so completion requires deciding and documenting a consistent treatment of team existence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100