Since then I try to install VB... and check many tips and tricks from the net, because it is still not working!
- I add the VB Dev. ID to system policy (spctl).
- add the 4 kext's to system policy
- I dis-/en-able master and check many time the status.
- I en-/dis-able SIP (csrutil) in recovery mode...
- Screenshot 2023-08-30 at 21.58.10.png (38.81 KiB) Viewed 3360 times
When I disable system policy master (spctl --master-disable) no change of behavior!
When I disable SIP in recovery mode and reboot... then VB is working fine! kextstat is showing the 4 kext's, no errors when starting machines...
(Remark: Ok, this is the result of a now paranoid company that wants to protect the operating system from administrators and only allow what it thinks is right... all by breaking down and bypassing BSD's security mechanisms in the past and now constructing and implementing maddening ones to protect its users from themselves.)
All the errors depends on the kext's, so what is wrong with this? But what is the reason that they are not accepted to load when SIP is enabled??? In system.log is nothing about kext or vbox, I found only success informations in install.log?
(Lulu, a small application firewall with kernel driver... I install, is working fine! What knows this developer more to do it right?)
One more Tip?
