keybase / keybase/client

security bug: upgrades and downgrades destroy keybase firejailing

Open
#9,757 0 comments 2 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

The keybase server (currently mislabeled as a "commandline client") has no proxy support. This means (amid other security issues) that diligent and defensive admins will modify the `run_keybase` script so as to prepend the executables with something like:
```
firejail --net=vnet0 --private="$(mktemp -d)" --profile=/etc/firejail/keybase.profile ...
```
When keybase is upgraded or downgraded, that code is silently reversed, leaving users defenseless. And worse, an upgrade can also occur silently (see https://github.com/keybase/client/issues/9756).

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue points to the run_keybase script and the upgrade/downgrade path, but names no repository file or test. Start by locating that script and the code or packaging flow that replaces it; verify upgrade and downgrade behavior, with completion defined as preserving firejail customization rather than silently reversing it.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
release, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.