Skip to content

Clear set-ID bits on Windows VM directories - #10046

Open
0bsolescence wants to merge 1 commit into
omacom:quattrofrom
0bsolescence:fix/windows-vm-clear-setgid
Open

Clear set-ID bits on Windows VM directories#10046
0bsolescence wants to merge 1 commit into
omacom:quattrofrom
0bsolescence:fix/windows-vm-clear-setgid

Conversation

@0bsolescence

Copy link
Copy Markdown

Fixes #9374.\n\nGNU chmod preserves set-ID bits on directories when applying a numeric mode, so a shared directory left at mode 2700 remained 2700 after chmod 0700. The following exact-mode check then rejected it and prevented the Windows VM from launching.\n\nUse an explicit symbolic mode that clears special bits while setting private 0700 permissions. Add a mount-boundary regression case starting with a setgid shared directory.\n\nTests:\n- bash test/shell.d/windows-vm-mount-boundary-test.sh (passes in an isolated privileged namespace)\n- ./test/all (Windows VM tests pass; five unrelated environment-dependent files fail because omarchy-pkgs is not checked out and the live desktop differs from test expectations)

@spuder

spuder commented Sep 3, 2026

Copy link
Copy Markdown

possible duplicate of #9783 #9605 #9564

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

windows-vm: chmod 0700 preserves directory setgid bit, causing launch to fail safety check

2 participants