feat: --allow-other flag for crm mount (fixes single-uid FUSE EACCES)#4
Merged
feat: --allow-other flag for crm mount (fixes single-uid FUSE EACCES)#4
Conversation
By default, FUSE mounts are accessible only to the mounting user — any process running as a different uid (e.g. root, container orchestrators enumerating /home/user) gets EACCES. That breaks consumers that need the mount to be readable from other contexts. Add a `--allow-other` CLI flag and matching `[mount].allow_other = true` config option. When set, the FUSE helper is invoked with `-o allow_other` so any uid can access the mount. The kernel still requires `user_allow_other` in /etc/fuse.conf when the mount is invoked by a non-root user; that's a deployment concern documented in the flag help text. Verified: - `crm mount ~/crm --allow-other` → root can lstat/read the mount. - `crm mount ~/crm` (default) → root gets EACCES (existing behavior). macOS NFS path is unaffected (the option only applies to the Linux FUSE mount).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Repro
Default FUSE mounts are accessible only to the mounting user. Any process running as a different uid gets EACCES on the mountpoint:
This breaks consumers that enumerate the parent directory from a different process context — e.g. an e2b sandbox SDK calling
files.list('/home/user')fails withlstat /home/user/crm: permission deniedeven though the mount is healthy from the user's own shell.Fix
Add a
--allow-otherCLI flag and matching[mount].allow_otherconfig option. When set, the FUSE helper is invoked with-o allow_other, which lets any uid access the mount. The kernel still requiresuser_allow_otherin/etc/fuse.confwhen the mount is invoked by a non-root user; that's a deployment concern called out in the flag help text.The macOS NFS path is unaffected — the option only applies to the Linux FUSE mount.
Verification
bun run check-typesclean.bun run buildclean.🤖 Generated with Claude Code