ok I read up on the sandbox.
IIUC, this applies to the installer/formula part. The app itself is still unsandboxed.
I can see that it closes one vector of attack (attacking the install script serving), but beyond that the user still runs the binary outside a sandbox.
I feel that the binaries themselves, both directly and indirectly (supply chain attack) are the elephant in the room.
Any thoughts on that?
I always wished the cli stuff I install from Homebrew was locked down by default, but it's not practical with today's computer systems since it kills usability.
Anyway, big fan of Homebrew. Looks like I can't submit a formula to core until I get more traction on GitHub (stars/forks/watchers).
Otherwise I have to go to taps which takes away a lot of the benefits of being on homebrew-core iiuc.
I can see that it closes one vector of attack (attacking the install script serving), but beyond that the user still runs the binary outside a sandbox.
I feel that the binaries themselves, both directly and indirectly (supply chain attack) are the elephant in the room.
Any thoughts on that? I always wished the cli stuff I install from Homebrew was locked down by default, but it's not practical with today's computer systems since it kills usability.
Anyway, big fan of Homebrew. Looks like I can't submit a formula to core until I get more traction on GitHub (stars/forks/watchers). Otherwise I have to go to taps which takes away a lot of the benefits of being on homebrew-core iiuc.