KBFS mounts as a "local disk" on Windows, but should be considered a network drive
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
The current behaviour causes issues when programs attempt to recurse through "all local drives" - for example, this is the default behaviour of WinDirStat, and when it tries to count up the file sizes inside K: things get really messy. Additionally, labeling as a local drive is misleading to the user, since KBFS won't work without Internet access.
I believe specially mounted drives on Windows do have control of what "kind" of drive they show up as, since VeraCrypt can mount drives as local or as removable. Could Keybase therefore change its mount behaviour and mark K: as a network drive instead?
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 Windows KBFS mount implementation and how it reports the mounted drive type to the operating system. Reproduce the current behavior with WinDirStat or another tool that scans local drives, then verify that the K: mount is identified as a network drive and no longer treated as a local disk.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100