Live data from Hacker News

How to check if your Apple Silicon Mac is booting securely

eclecticlight.co

1–10 of 23 posts

Re: How to check if your Apple Silicon Mac is booting securely

#3

s/booting securely/running only the code Apple approves of/g

You can run unverified code if you build it yourself. You can distribute unverified code by just paying $99/year to Apple. Not great, but still no need for specific code approval.

Re: How to check if your Apple Silicon Mac is booting securely

#6
post #4

I had to do this today for a Universal Audio Apollo audio interface. Glad it’s on a dedicated machine. https://help.uaudio.com/hc/en-us/articles/360057137692-Apple...

Interesting. They need that for lowest-possible latency? And it should be fairly safe?

Re: How to check if your Apple Silicon Mac is booting securely

#7
post #3

s/booting securely/running only the code Apple approves of/g

You can run unverified code if you build it yourself. You can distribute unverified code by just paying $99/year to Apple. Not great, but still no need for specific code approval.

Not if you want to use some features like bridged networking. For that you need to go and beg Apple for an entitlement. Or you have to disable SIP entirely.

Re: How to check if your Apple Silicon Mac is booting securely

#8
post #7
post #3

Earlier quoted context omitted.

You can run unverified code if you build it yourself. You can distribute unverified code by just paying $99/year to Apple. Not great, but still no need for specific code approval.

Not if you want to use some features like bridged networking. For that you need to go and beg Apple for an entitlement. Or you have to disable SIP entirely.

They respond to the begging as incredibly well as they respond to feedback/bug reports, right?

Re: How to check if your Apple Silicon Mac is booting securely

#10
post #6
post #4

I had to do this today for a Universal Audio Apollo audio interface. Glad it’s on a dedicated machine. https://help.uaudio.com/hc/en-us/articles/360057137692-Apple...

Interesting. They need that for lowest-possible latency? And it should be fairly safe?

Assuming they're USB devices they shouldn't be a reason to do this... Apple moved third-party drivers for USB devices and audio HAL extensions to user space, so there's some minor overhead choosing DriverKit over IOKit. Everything I've dug up says it's low single digit percentages. I wouldn't be developing USB drivers against IOKit anymore personally and I'd be looking to move over pretty aggressively before Apple drops the hammer.
Post reply on HN