-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Whitelisting of Kext's #24
Comments
Sure, @egandro, I'd be happy to consider a PR that adds such a feature, thought it does does seem like it may contradict the
I think I'm willing to make an exception here, since On the other hand, I wonder if it would be better to make this mechanism more generic; basically, a way for the user to specify a custom script that is run after the macOS installer finishes, and is provided with the path to the newly-installed OS so that it can make any modifications it wants. |
I think yes - if we provide some cool examples. |
The user script you want would look something like:
To determine what values you need to insert into the KextPolicy database, first install the kexts on a running system and permit them to be loaded, and then run this command:
|
I've merged the PR to master: bcc8f9f |
Tagged and released: https://github.com/bacongravy/macinbox/tree/v3.3.0 |
Hello,
can we make a nice --whitelist-known-kext flag?
I'd like to whitelist all "wellknown" kext e.g. vbox, virtualbox, docker, ... by the way you use for vmware.
This will reduce the number of clicks we have to do in postsetup.
(I will create a patch request within a few days).
The text was updated successfully, but these errors were encountered: