How to install?

[huddx01]

Hi,

thanks for porting this tool to macOS. Would be very useful for me...

would like to try it out, but neither installation of the SystemExtension via brew succeeds, nor manual via git clone and trying install the Extension after a successful development build (I only own a "non paid" dev cert)...

I am on latest Sequoia and Silicon M1.

via brew:

• Installation went flawlessly.

Found Contents directory, reconstructing system extension bundle...
System extension bundle created at: /opt/homebrew/Cellar/usbip/0.1.38-test/Library/SystemExtensions/USBIPDSystemExtension.systemextension

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
  🔧 Additional Setup Required
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

To complete installation and enable system extension functionality:

  1. Install the system extension:
     sudo usbipd install-system-extension

  2. Start the service:
     sudo brew services start usbip

  3. Approve the system extension in:
     System Preferences → Security & Privacy → General

• after this, it stucks at 30% (see last lines)
• I would expect to see sth like "Allow installation of new System Extension" in Settings - Privacy & Security - Security in Allow applications from ... But I don't see anything there

sudo usbipd install-system-extension
Password:
Starting System Extension installation...
This will register the System Extension with macOS and may require user approval.

[██████░░░░░░░░░░░░░░]  30% System Registration: Submitting System Extension to macOS for approval...2025-09-18 00:02:30.974 [INFO] SystemExtensionInstaller initialized
2025-09-18 00:02:30.973 [DEBUG] Starting System Extension bundle detection
2025-09-18 00:02:30.983 [DEBUG] Attempting production bundle detection (Homebrew)
2025-09-18 00:02:30.983 [DEBUG] Found production bundle (.systemextension) {bundlePath=/opt/homebrew/Cellar/usbip/0.1.38-test/Library/SystemExtensions/USBIPDSystemExtension.systemextension, bundleType=production}
...
2025-09-18 00:02:30.987 [INFO] Starting complete System Extension installation workflow
2025-09-18 00:02:30.987 [INFO] Installation progress {phase=bundle_detection, message=Detecting System Extension bundle..., progress=0.1}
2025-09-18 00:02:30.987 [INFO] Performing bundle detection
2025-09-18 00:02:30.987 [INFO] Bundle detection succeeded {bundlePath=/opt/homebrew/Cellar/usbip/0.1.38-test/Library/SystemExtensions/USBIPDSystemExtension.systemextension, environment=homebrew(cellarPath: "/opt/homebrew/Cellar/usbip/0.1.38-test/Library/SystemExtensions", version: Optional("0.1.38-test"))}
2025-09-18 00:02:30.987 [INFO] Installation progress {phase=system_extension_submission, progress=0.3, message=Submitting System Extension to macOS for approval...}
2025-09-18 00:02:30.987 [INFO] Performing System Extension submission {bundlePath=/opt/homebrew/Cellar/usbip/0.1.38-test/Library/SystemExtensions/USBIPDSystemExtension.systemextension}
2025-09-18 00:02:30.974 [INFO] ServiceLifecycleManager initialized {homebrewPrefix=/opt/homebrew}

Any ideas?

[huddx01]

Ok, got it... The installation via brew cannot work at the current state.

Maybe useful for others:
This didn't work, because SystemExtensions and NetworkExtensions have to be signed with a developer cert which has the additional entitlements.
Additionally, for a proper (=without disabled SIP, etc...) installation/use the developers embedded.provisionprofile has to be placed into the app package, too.
Same for ./Library/SystemExtensions/USBIPDSystemExtension.systemextension inside the app package....

[beriberikix]

@huddx01 sorry for the confusion and thanks for the interest. I'll update the Readme soon.

You're spot on - we've been waiting for Apple to review our request for the entitlement for over 2 months now. Unfortunately, they keep responding, "it's under review."

Hopefully we'll see movement on the review process and can actually return to development. Until then, this is basically not usable to users.

[MikkelIJ]

Very cool tool, I really hope this issue gets resolved soon :O
Does it work if I build it from Xcode with my own provisioning profile or certificate ??

[huddx01]

@MikkelIJ yes, should work, if your cert has the mentioned entitlements. You might need to request Apple to get them.

Maybe to add: It works without a dev cert which has the entitlements, but you'll need to disable SIP.
Then, in each targets Build Settings, add a user-defined setting "AD_HOC_CODE_SIGNING_ALLOWED". Set it to YES.
In the Signing section, you are able to set "Sign to Run Locally" now...

@beriberikix seems your entitlement is still not approved? If yes, my personal experience is, that apple has a problem with the code or sth.... Usually it takes 2-4 weeks (afaik)...
However, a possible show stopper by apple seems to be that the extension is not bundled inside an app. An App needs to be installed in /Applications folder. Additionally the dext needs to be placed in the App's Contents/Library/SystemExtensions folder, to fulfill Apples "Rules"...

[CircuitCaster]

@beriberikix Did you try the approach to bundle the extension into an app in the meantime?

[beriberikix]

Sorry for the run-around — the instructions you followed were wrong, not your reading of them. Everything in that post_install block has been removed, and installation is much simpler now.

The System Extension was never going to work that way. sudo usbipd install-system-extension could not succeed from a Homebrew prefix: OSSystemExtensionRequest resolves extensions inside the calling app's bundle and requires that bundle to live in /Applications, so the staged bundle was never consulted. The command has been removed from the CLI, the bundle is no longer staged by the formula, and the instructions are gone. Your unpaid dev cert was not the problem.

Installing v0.5.1 on Apple silicon:

brew tap beriberikix/usbipd-mac
brew trust beriberikix/usbipd-mac   # Homebrew now requires this for third-party taps
brew install usbip

That brew trust step is new and easy to miss — without it you get Refusing to load formula ... from untrusted tap. I hit it myself testing this today and have not yet added it to the README.

Then:

usbipd list                    # see attached devices
usbipd bind <busid>            # offer one for sharing
sudo brew services start usbip # or: usbipd daemon

Please check what you want to share before investing time. This works for devices macOS has not bound a driver to — debug probes (J-Link, ST-Link, CMSIS-DAP), boards in DFU or bootloader mode, Android devices in ADB mode, vendor-specific interfaces. It cannot serve anything macOS claims: USB-serial adapters, HID, mass storage, audio, cameras. bind now refuses those up front and names the owning driver, rather than accepting and failing later:

$ usbipd bind 1-19
Cannot share 1-19: macOS has bound a driver to it (AppleUserHIDDevice).

That is a hard limit without a DriverKit entitlement, which Apple declined in February. ./Scripts/validate-usb-entitlements.sh will tell you which of your own devices fall on which side.

If you are on Intel rather than Apple silicon, see #32 — the published binaries are arm64 only at the moment.