Repository navigation
Explain prefix owner trust when using sudo - #508
Conversation
- Document the root privileges entrusted to the prefix owner and anyone who can modify Homebrew's code when an administrator invokes `sudo brew`. - Explain that edits to `bin/brew` and its loaded code take effect before command-specific checks or a switch to another user. - Apply the same trust model to commands that only display information and commands that later run as another account. - Include an example of a prefix owner adding a deletion command to the `brew` entry point before its next invocation with `sudo`. - State that changing ownership of selected paths retains trust in accounts that can still modify Homebrew's code. - Distinguish Homebrew-managed install, post-install and test execution from installed software that the user subsequently chooses to run. - Cover installed software launched through Homebrew commands or registered for automatic startup at the privileges the user requests.
|
No actionable comments were generated in the recent review. Summary
Merge Risk:
|
sudo brew.bin/brewand its loaded code take effect before command-specific checks or a switch to another user.brewentry point before its next invocation withsudo.