Apple kernel extensions are not signed after installing Ventura on MacBook Pro

Ah, sorry. Gotcha'. Another one of those folks who post just for the sake of being contrary and stir up trouble. I got that impression with the next response referring to you as a "character".

But of course, not quite soon enough as I responded again. Last one, though. There's nothing else to say.

Kurt Lang wrote:

My response was to TopGun2 about eugene. The post was made just yesterday.

Yes. I know. You are responding to the stalker. Do you want his e-mail address? I can send it to you. You and him can spend years debating the malicious intent behind Graphic Converter's inadequate Facebook presence. But wait, you've recommended Graphic Converter in the past, haven't you? Maybe you are actually one of the "bad guys" like me. Two peas in a pod, I'd say.

Eugene left the chat almost 9 months ago.

My response was to TopGun2 about eugene. The post was made just yesterday.

Kurt Lang wrote:

Agreed. But I figured simply saying eugene's statement was "wrong" wouldn't mean much without clarification.

It doesn't mean anything at all. Eugene left the chat almost 9 months ago. Your metacarpals will turn to dust long before you ever manage to "clarify" anything to cyber-stalker. You will fail - guaranteed. He will be back in a month, or a year, asking about kernel extensions, ClamXAV, EtreCheck, with a new alias if this one gets banned too. The only winning move is not to play. Do not respond. Do not challenge. Do not insult. Do not engage at all.

If you sincerely want to try anyway, I would humbly request that you do it in Usenet, where you and his other disciples can spend your golden years in endless rounds of mutual insults and stalking side-quests.

Agreed. But I figured simply saying eugene's statement was "wrong" wouldn't mean much without clarification.

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.

Before Catalina, you could do pretty much anything you wanted to the drive contents. In Catalina, it's more difficult but can still be done.

In Monterey, Ventura or Sonoma, you can't touch the system. I tried it on both a 2018 Intel mini, and an M2 mini Pro. Both running Sonoma.

I disabled SIP, which you can do on both. But, you can't mount any drive to modify it. Trying the old command…

mount -uw /

…produces a message that this old command cannot be used. So I tried a current command…

mount /dev/disk3s9

…with disk3s9 being a specific drive division of many you can get with a diskutil list command. I tried mounting the system drive, the user data drive, and even an unprotected volume with nothing on it but my personal stuff. The result was always the same message:

invalid special file or file system

Trying to invoke sudo does nothing. You get the message:

command not found

So, if you're using Monterey or later, there's nothing to concerned about at all.

If you turn off SIP in Recovery Mode and then mount root you can write to any folder including /System/Library/Extensions

Just how concerned about that should one be, Eugene?

Are you still concerned about matters?

Since it is not as you wish it would be, you should wipe it and reinstall. Then, when you check again and it isn't as you wish it to be, wipe and reinstall. Rinse, repeat.

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.

Steady on my friend.

There are some who seek a moment of fame.

Then there are others who want a serious solution to a technical Apple software hardware issue.

Think there has been enough technical information supplied from various contributors for OP to reach a reasonable conclusion on this issue

It's irrelevant whether they're signed or not. They're in the System folder. Only Apple - literally - can put anything there.

Not really sure what that means