Today, I’d like to announce Homebrew 5.0.0. The most significant changes since 4.6.0 are download concurrency by default, official support for Linux ARM64/AArch64, timescales for deprecating macOS Intel and removing macOS Gatekeeper bypass behaviours.
Shame on you, Homebrew, for effectively killing FOSS apps from casks.
--no-quarantine is used to forcibly bypass Gatekeeper, which is a built-in macOS security mechanism. This is used to run unsigned/unnotarized applications.
With the above in mind, it’s time to deprecate the --no-quarantine flag from brew. It intentionally bypasses macOS security mechanisms, which we already actively discourage. Deprecating now will give a decent lead time for users using it to come up with another solution or adjust their workflows.
Yes, but you can still compile the code yourself. It’s only problematic for binary distribution. This is basically a question of balancing security vs. freedom I suppose.
Their explanation as to why:
The adjusted solution/workflow: use something other than homebrew
I mean, theres macports and what else? Is macports even kickin still? No other package managers other than homebrew
Pretty sure it’s still around. Nix is an option as well.
How will these other solutions bypass Apples quarantine?
By doing what homebrew currently does when you pass the
--no-quarantineflag, which is callxattr.Note that I’d probably support removing
--no-quarantineif Apple’s notarization service was free.Notarisation, free (as in beer) limits your ability to run your code that (Corporate) doesn’t like, making it inherently non free (as in freedom).
Yes, but you can still compile the code yourself. It’s only problematic for binary distribution. This is basically a question of balancing security vs. freedom I suppose.