Backup software thinks /keybase is a folder that should be backed up, and then fails when it can't be accessed by root.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Keybase GUI Version: 1.0.20-20170309192151+e30557a
When trying to back up my computer with any backup agent that uses administrative privileges to perform backups, they universally report filesystem errors trying to access /keybase/ to back it up.
This is probably because 'root' has no keybase configuration. It may make sense on Mac to handle this specific case more effectively, so that backup clients either back up nothing (which is fine) or ignore the mount (because you tune it to look like a network mount, or something, which is also fine) or some other manner altogether.
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
No source file, test, or entry point is named. Start by reproducing the backup failure on macOS with an administrative backup agent and inspect how /keybase is exposed and accessed by root. Done means backup software no longer reports filesystem errors for /keybase, with the chosen handling documented or tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100