Post

Replies

Boosts

Views

Activity

Reply to Develop DriverKit extensions locally with a Free Developer Account
As a minor note, I think disabling SIP is sufficient, which is significantly less dangerous than disabling AMFI. I must have done something wrong because I wasn't able to get it working without (temporarily) disabling AMFI. My personal recommendation would be to pay for a yearly developer membership, but if that's not possible then, yes, the alternative would be to disable SIP. I may decide to purchase a paid developer account in the future, but I do not think installing personal-made drivers for personal use on personal devices should require a choice between a yearly subscription or disabling important security mechanisms. That's certainly something you can file a bug asking us to support, but I wanted to make it clear what you were asking for. Where would I file such a request (/ "bug")? Even if filed, I worry that it is unlikely for this issue to be addressed in reasonable time.
Topic: App & System Services SubTopic: Drivers Tags:
2d
Reply to Develop DriverKit extensions locally with a Free Developer Account
Thanks for the incredibly helpful reply! I was able to successfully load the extension, but it did require disabling AMFI as you suspected. We restrict registration like this to help close out the opportunity for "mischief" and abuse that allowing unrestricted registration could create. Unfortunately, this does mean those with free developer accounts must defang important security protections (SIP, AMFI) in order to install our own DriverKit extensions for personal use. Would it be possible to request an exception in this case for my free developer account?
Topic: App & System Services SubTopic: Drivers Tags:
4d
Reply to Develop DriverKit extensions locally with a Free Developer Account
As a minor note, I think disabling SIP is sufficient, which is significantly less dangerous than disabling AMFI. I must have done something wrong because I wasn't able to get it working without (temporarily) disabling AMFI. My personal recommendation would be to pay for a yearly developer membership, but if that's not possible then, yes, the alternative would be to disable SIP. I may decide to purchase a paid developer account in the future, but I do not think installing personal-made drivers for personal use on personal devices should require a choice between a yearly subscription or disabling important security mechanisms. That's certainly something you can file a bug asking us to support, but I wanted to make it clear what you were asking for. Where would I file such a request (/ "bug")? Even if filed, I worry that it is unlikely for this issue to be addressed in reasonable time.
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
2d
Reply to Develop DriverKit extensions locally with a Free Developer Account
Thanks for the incredibly helpful reply! I was able to successfully load the extension, but it did require disabling AMFI as you suspected. We restrict registration like this to help close out the opportunity for "mischief" and abuse that allowing unrestricted registration could create. Unfortunately, this does mean those with free developer accounts must defang important security protections (SIP, AMFI) in order to install our own DriverKit extensions for personal use. Would it be possible to request an exception in this case for my free developer account?
Topic: App & System Services SubTopic: Drivers Tags:
Replies
Boosts
Views
Activity
4d