in reply to Establishing a beachhead and acquiring privileges on a Mac-mini

root or otherwise, you are not allowed access to /usr/bin and lots of other locations and operations which traditionally root had, in *nix. There is a way to bypass this (with something called "bypassing the SIP", not sure if you will ever be 100% root though!). Which I have not tried and do not recommend. Just get used to the fact that the notion of my computer is well behind us at least with Apple and Microsoft. To me, it seems their difference is that while MS trusts the security of its OS to illiterate IT operators brainmassaged sufficiently with """MS Engineer""" (top oxymoron) courses aspiring to that particular moustache style, Apple trusts no one but its own breed at cupertino.

I faced more problems, like code signing. And that homebrew does not support older OSX versions (and works 50-50 edit: for my 10-year hardware not allowed any more OS upgrades). And that you need that dreaded XCode for anything to be compiled. And the system becomes unworkable for the average bloke once the hardware's age forbids software upgrades. I personally use my old macbook for watching the occassional movie. And even that presents a challenge...

For some binaries, Homebrew refuses to install them in locations which shadow the system default. That's another caveat you need to juggle.

Q3: brew analytics off - though this is your least of the privacy problems as Apple keeps phoning home more than a butterboy in summer camp. (hint: pay Lulu a visit pronto and learn how to ban ip addresses using /etc/hosts)

Replies are listed 'Best First'.
Re^2: Establishing a beachhead and acquiring privileges on a Mac-mini
by karlgoethebier (Abbot) on Apr 22, 2023 at 11:40 UTC
    «…I have not tried and do not recommend.»

    That's almost like saying: I don't know but I can't recommend it. In general, the whole argumentation is too much propaganda for me. I am actually also sure that there are reasonable, practicable solutions for the problems mentioned. You will have to search for them a bit. But Apple's documentation is not bad. In fact, it is mostly excellent. But many don't know that or don't want to admit it.

    «The Crux of the Biscuit is the Apostrophe»

      The reason I have not tried and do not recommend this is because I don't know the consequences of this action and do not trust Apple, or any other profit-maximising corporation, to tell me exactly what these consequences will be.

      I am primarily concerned that this action may unlock back-doors or activate some bug which may decrease OS security in other, undocumented, ways additionally to what Apple states in the link about SIP (which you posted). I am also afraid that this bypassing the SIP could be a "challenge" to lure those still seeking Absolute Freedom in OS into trying it out and then Apple opening a huge backdoor on them and on top of that lecturing them with a "I told you so" as the cherry in the pwned pie.

      The OS I trust, use and recommend is Linux. For Linux, I have done and recommended things equivalent to bypassing the SIP. But I will not do that for Apple. It's not FUD, it's not propaganda. It's just like refusing candy from a stranger, or an apple from the serpent. As simple as that.

      bw, bliako