53 ms·

Yeah seem like a limitation of the third party kext more than anything. It sucks but i don't see how this is a MacOS or a M1 issue. It's not like this kext was

Yeah seem like a limitation of the third party kext more than anything. It sucks but i don't see how this is a MacOS or a M1 issue. It's not like this kext was able to run without downgrading security previously.

Maursault 4y ago
> downgrading security Used in article, but only you and GP have mentioned. What is this garbage nomenclature? First of all, what in God's name does "security" mean in this context? It is obviously supposed to stand for somethings specific, this is not just an in general mention of security. What? And "downgrading?" What is happening here? I am completely and utterly lost on this word and why it is used, here, in this context (the article author's use... and since both you and GP used it, I hoped either could explain to me what is going on with security downgrade like this is a thing, when I expect it really isn't a real thing, someone chose bad words for nonissue, but if not, thx).
- Twisell 4y ago
  I'll try but by all mean do your own research, it's not in my comfort area of expertise. It refer to System Integrity Protection* on MacOs which when enabled (by default) is supposed to tightly control which and how privileged code is allowed to run at kernel level. https://support.apple.com/fr-fr/guide/security/sec8e454101b/web https://support.apple.com/fr-fr/guide/security/sec8e454101b/... It seems like OP issue is that in order to run a third party legacy kernel extension that doesn't follow most recent guidelines he need to disable this safety altogether for the whole OS. (And there is a separate issue because the third party legacy kernel installer require all external storage to be unmounted at install time, thus preventing installation on an external storage) I tried to be clear, english is not my mother thong, hope it might help. *Edit : System Integrity Protection is maybe the more adequate term instead of secure boot
  - Maursault 4y ago
    Thank you. So, "security" is System Integrity Protection, a feature of macOS, and "downgrading" merely means disabling it. Sounds like a great big nothing burger.

Maursault 4y ago

> downgrading security Used in article, but only you and GP have mentioned. What is this garbage nomenclature? First of all, what in God's name does "security" mean in this context? It is obviously supposed to stand for somethings specific, this is not just an in general mention of security. What? And "downgrading?" What is happening here? I am completely and utterly lost on this word and why it is used, here, in this context (the article author's use... and since both you and GP used it, I hoped either could explain to me what is going on with security downgrade like this is a thing, when I expect it really isn't a real thing, someone chose bad words for nonissue, but if not, thx).

Twisell 4y ago
I'll try but by all mean do your own research, it's not in my comfort area of expertise. It refer to System Integrity Protection* on MacOs which when enabled (by default) is supposed to tightly control which and how privileged code is allowed to run at kernel level. https://support.apple.com/fr-fr/guide/security/sec8e454101b/web https://support.apple.com/fr-fr/guide/security/sec8e454101b/... It seems like OP issue is that in order to run a third party legacy kernel extension that doesn't follow most recent guidelines he need to disable this safety altogether for the whole OS. (And there is a separate issue because the third party legacy kernel installer require all external storage to be unmounted at install time, thus preventing installation on an external storage) I tried to be clear, english is not my mother thong, hope it might help. *Edit : System Integrity Protection is maybe the more adequate term instead of secure boot
- Maursault 4y ago
  Thank you. So, "security" is System Integrity Protection, a feature of macOS, and "downgrading" merely means disabling it. Sounds like a great big nothing burger.