Installing Homebrew in a sandbox #4325
Replies: 1 comment
-
That's likely because:
No, because reason [2] above. However, there's a cross-platform way to get the same effect: set the account password to a random string of decent length (I suggest at least 16 characters, generated by a password manager), then throw that password away.
Sure. You could just create a normal user account and not turn stuff off. Why do you feel the need to hide that account? Personally, I'd:
Sounds like you've got an over-broad then you're forcing which just replaces URLs to my own account with my local SSH host shortcut. After all, I neither need nor intend to modify Homebrew's own repos. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Output of
brew configOutput of
brew doctorDescription of issue
Platform: MacOS
From the FAQ:
Observations:
brew)Goal: install homebrew in a sandbox such that any homebrew files can only be updated by a specific "homebrew" account.
What I did:
sudo dscl . create /Users/hiddenuser IsHidden 1)This mostly works. The primary goal is met: homebrew can be updated by going
sudo -u homebrew -Iand then doing whatever I need to, but otherwise is read only. Also, homebrew can't write to my files, and I can't write to homebrew's files.Remaining issues:
Installation notes:
Homebrew tries to set the remote to https://github.com/Homebrew/brew . I could not get this to accept my user name and password while running effectively headless. I got it to work by setting up ssh keys and then setting
HOMEBREW_BREW_GIT_REMOTEandHOMEBREW_CORE_GIT_REMOTE, togit@github.com:Homebrew/brew.gitbut this required trawling the install script.Beta Was this translation helpful? Give feedback.
All reactions