fix(security): deny raw factotum grants - #462
Merged
Merged
Conversation
pdfinn
force-pushed
the
audit/factotum-path-deny
branch
from
August 4, 2026 06:03
1f8467d to
c7e6998
Compare
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.
Summary
Security rationale
Factotum is the credential boundary. It is intentionally auto-mounted only for selected fixed-function tools and withheld when arbitrary exec/shell is present. A raw /mnt/factotum path grant bypasses that mediation and can hand the credential service to arbitrary tools, so it should be treated as a privileged control-capability root rather than a generic filesystem path.
Tests