keybase / keybase/keybase-issues
Keybase permissions and sudo requirements on OSX Yosemite
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
This isn't an issue per-se, but i wanted to point out for any osx yosemite users that you don't have to keep using sudo or root to run keybase.
You needed root to run all the installation commands on yosemite, but that's due to the permissions structure and all for installing programs
If you wish to use keybase as a non-root user, you would have to basically run, assuming you have installed keybase using sudo or root (post install):
sudo keybase login
chown -R ~/.local
chown -R ~/.gnupg
chmod 600 ~/.gnupg/gpg.conf
I'm not sure why gpg.conf was left with group and other r+x permissions, but on my other system i have it as 600 so i have adjusted it to reflect here.. works perfectly now without requiring sudo, and it stops throwing errors or warnings.
Hopefully devs can work out a way to add the chown/chmods into the standard login procedure for yosemite users.
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 reviewing the reported Yosemite post-install commands: sudo keybase login, chown on ~/.local and ~/.gnupg, and chmod on ~/.gnupg/gpg.conf. Reproduce the non-root login path and verify that installation leaves these paths usable without sudo and without permission warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, macos
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100