Just made clean installation of macOS Ventura from USB stick over Big Sur, preserving Bootcamp partition.
I was really surprised, seeing that the Apple OS kexts are not signed and not loaded (most of them).
Is it normal situation, or should I immediately wipe out this installation?
(Intel MacBook 2018/32G/1Tb/Rad560x)
[Re-Titled by Moderator]
MacBook Pro 13″, macOS 10.14
eugene.davidson wrote:
Is it normal situation, or should I immediately wipe out this installation?
It's normal. The operating system lives on a cryptographically signed snapshot. For compatibility reasons, there are stubs of various files in the normal filesystem. But the actual executables aren't present. Therefore, when you check the code signature, it fails. But that's OK, because none of these extensions are actually loaded from those locations. They are loaded from one of the other system locations. That's why none of those extensions are reported as loaded, because they aren't. But if you check using kmutil, you'll see that many of them actually are loaded.
Most kernel extensions load as needed.
They don't need to be signed.
This was the duplicated post
Not really sure what that means
I would accept this statement if ALL kernel extensions were unsigned. But as you can see this is not the case. This seems odd
It's irrelevant whether they're signed or not. They're in the System folder. Only Apple - literally - can put anything there.
Kurt Lang wrote:
there's nothing to concerned about at all.
I can assure you that Mr. Cyber-stalker has nothing to be concerned about.
Agreed. But I figured simply saying eugene's statement was "wrong" wouldn't mean much without clarification.
Eugene left the chat almost 9 months ago.
My response was to TopGun2 about eugene. The post was made just yesterday.
Apple kernel extensions are not signed after installing Ventura on MacBook Pro
