Any downside to turning off SIP in a VM?

[Jason Liu]

To answer the question posed in the subject line, turning off SIP inside of
a VM is probably the best (and safest) way to test what the implications of
turning SIP off on a system might be. Since the VM is completely
self-contained, turning off SIP won't affect anything outside of it. I
routinely turn off SIP on the macOS VMs I use for development and testing,
and the one and only downside that I can think of is that if you hose the
VM, you will have to either restore a snapshot or recopy the virtual hard
disk from that copy you made before trying to undertake any potentially
VM-hosing actions.

-- 
Jason Liu


On Fri, Oct 4, 2024 at 4:58 PM Mark E Anderson <mark at macports.org> wrote:

> Because I refuse to let qt5-qtwebengine beat me, I've been running
> macports in VMs to test what the heck is going on with patching ninja
> files. Trace mode will work better if I turn SIP off, correct? But if I do,
> will things succeed that should fail? Or should I worry about that later,
> since they'll get tested on the build bot and CI?
>
> —Mark
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20241004/00484343/attachment.htm>