adding other csr-active-config check for patching kext

jacklukem commented 4 years ago

https://github.com/barrykn/big-sur-micropatcher/blob/a611c168cb446dbeb0f1d967856e010ed5ddc9af/payloads/patch-kexts.sh#L43

Could you consider to add something as:

if (! nvram csr-active-config | grep -q '%7f%0[89]%00%00$') && (! nvram csr-active-config | grep -q '%ff%0f%00%00$') && (! nvram csr-active-config | grep -q 'w%0[89]%00%00$')

in that way those who used my USBopencore w%09%00%00 or BaseSystem fix (where ASentientBot 0xfff patched boot.efi is used) could apply your Micropatcher kext patches with a snapshot booting.

Also if someone has a snapshot booting disabled with working sudo mount -uw / even only with w%00%00%00 (0x77 standard Catalina and Mojave SIP disabled) is suffice to apply any kmutil BigSur kext patches (but snapshot disabled is not frequent so I edited that value).

Moreover since with the new 0x7F csrutil value for BigSur, Catalina and Mojave SIP is in custom configuration, I guess apple might decide to set again csrutil authenticated-root as w%08%00%00 , mainly to keep a Catalina valid SIP disabled, because they weirdly updated it to 10.15.7 .

So having multiple allowed csrutil configurations should let apply your BigSur kext patches to different machines.

barrykn commented 4 years ago

I think I should do the following:

Add the other values like you did (I might turn it from an if statement into a case statement while I'm at it)
Add a --force command line option to bypass the check

I'll do this for v0.3.4.

barrykn commented 4 years ago

Note to self: Make sure these changes get merged into remount-sysvol.sh as well. If not for v0.3.4, then for the release after.

barrykn commented 4 years ago

Fixed in v0.4.0, so closing this issue. Please reopen this issue if it is not adequately fixed.

barrykn / big-sur-micropatcher

adding other csr-active-config check for patching kext #59