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

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.

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.

" Compromised " in what way ?

Only as a point of interest >>

Starting in macOS 11 Big Sur and above. 

The Operating System resides in a Sealed and Read Only Volume that can not be opened by the User nor by Third Party Applications.

The only Entity that can open and modify or alter this Volume is Apple.

That would occur when a update or UpGrade is performed.

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.

The System folder of the OS (where all of these are located) is completely and cryptographically locked down. There is no way for anyone to compromise anything installed by the OS. And that includes everything in the Applications and Utilities folders installed with the OS.

There's also no need for Apple to sign their own work. That's basically saying, "I trust myself.", which is redundant.

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.

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.

I see nothing unusual

Point of reference for Screen Shot below

This is from an Apple Silicon Computer originally coming with Big Sur macOS 11, upgraded to Monterey macOS 12 and now on Ventura macOS 13.5

eugene.davidson wrote:

Kernel extensions are important operating system drivers, all of these were signed and loaded in Big Sur. So I think they switched to another kext control mechanism, just need to make sure. Otherwise, it looks like the OS was compromised.

What you see is normal.

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

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.

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