Topic: 4.30 update detour
I just went through running the Driver Kit 4.30 installer (DK), with v4.27 successfully installed since January or something in macOS 14.8.7 Sonoma. As I already had this previous version installed and working I did not do the kernel driver (KD) first, as I haven't done that since moving to the then beta on Ventura, but I went into Privacy & Security just in case. There was nothing at all in there, but an OK dialog showed up in its own window stating
"Error loading RME USB
DriverKit extension
Code Signature Invalid"
I rebooted anyway and had no audio interface (OG Babyface), so tried installing again, with same outcome. I was thinking I could reset by doing the kernel install instead, so tried that and was surprised to discover I had already lowered security, so went ahead. This time the dreaded "System extension blocked…signed by RME GmbH" and "needs to be updated" message.
At no point was there any Allow button in Privacy & Security. I wonder if this might be something that has changed with Sonoma updates.
I tried once more after deleting installed items manually and a new reboot and gave up after the same thing again, going back to reinstalling v.4.27 anew. This time this as well resulted in "Code Signature Invalid" so puzzled I investigated the installer with codesign in Terminal and some other tests. Most checked out, so extracted the payload and most checked out fine but got this surprising result of
pkgutil --check-signature:
"Package "RMEFirefaceUSB.kext":
Status: signed by untrusted certificate
Certificate Chain:
1. Developer ID Application: RME GmbH (67AK2U2X7M)
SHA256 Fingerprint:
A2 B4 6B 4E 5E 8C 25 46 F9 6A 16 8D 25 C9 0B A2 5A 9C D1 3C 28 D1
39 A9 DC 51 DF DD 4B 4E 22 62
………"
How's this? v4.27 was installed once and working. I assumed it was a red herring as this was in the installer not where it will end up. Looked around some more and tried one more time, nothing to OK and rebooted. Now 4.27 was up and running no problem as before this started.
Am I any wiser? Not really, but it feels like maybe Apple changed how macOS 14 Sonoma behaves with the updates, or I'm missing something. Considering I now could find out that plutil reveals that what's loaded for USB is:
"identifier" => "de.rme-audio.dkusb" "originPath" => "/Applications/Fireface USB Settings.app/Contents/Library/SystemExtensions/de.rme-audio.dkusb.dext"
"relative" => "file:///Library/SystemExtensions/[SOME UUID code]/de.rme-audio.dkusb.dext/
…so no RMEFirefaceUSB.kext is actually installed. Not that I could find anyway.
What might I have missed here? I want 4.30, for no real reason, so will try later.