keybase / keybase/keybase-issues
keybase-installer nfs assumption
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
keybase installer wants to run as root; this is fine with sudo. However, after verifying the signature of the downloaded keybase, it attempts to chown '$HOME/tmp/npm-###/package/package.json'. Of course, nfs (root-squash) maps root into nobody, and nobody cannot chown a file, so the install bails.
Why did the installer switch from using /tmp (which is local and therefore root accessible) to $HOME/tmp where root is squashed? I humbly suggest, it should drop root privledges ASAP, or else stay in a local filesystem...
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 locating the keybase installer logic that uses $HOME/tmp/npm-###/package/package.json, then reproduce the failure with an NFS home directory using root squash. Done means installation no longer fails at the chown step when running through sudo, while preserving signature verification.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100