Signed Driver Sponsorship Status

[MatthewRasa]

Hi folks,

From reading through the recent issues and discussions, it seems that we are (hopefully!) on the path toward a sponsorship for getting the kernel drivers signed. I was curious what the remaining steps / timeline looks like for this, and if we have a place for tracking that?

If it's not already being tracked and you think it makes sense to do so, we can use this discussion for tracking purposes.

[scheibling]

Since we use this software on a regular basis, we'd be open providing the required signatures for the release packages/driver catalogues as long as we can find a decent way to secure that certification pipeline (approval flow and/or some technical safeguards). We already have the necessary EV certificates.

One thing that might be worth looking into though is Azure Trusted Signing, it's quite a few leagues cheaper than a full-on EV certificate, and from what I've been able to find out it should cover the drivers in this package and the MSI file. Let me know if you wanna test that option, we have a verified account there as well and I'd be happy to sign a few files to test it out to start - if that's an alternative those certificates can also be issued to developers and not just established companies, meaning you'd be able to handle all that on your own for a reasonable cost and not depend on some third party.

Nevermind that last part, missed that it's not currently a UM driver.

[Andreyokey]

Hello there, Is there any way I can use usbip-win2 without Test Mode enabled? I looking for help—maybe there's a way to self-sign the drivers or bypass the restrictions? Scheibling, would you be able to share the method you used to sign the drivers or possibly the signed drivers themselves?

[Andreyokey]

I understand that the issue is most likely on the USBIP server side. Certainly all users encounter this problem, and in my opinion it's critical — the server cannot detect improperly disconnected clients, and USB devices are only released after manually executing unbind.
I could write a script to automatically disconnect devices when a client disconnects, but this only works in the case of 1 USB and 1 client. The difficulty is that when using multiple USB devices and multiple clients, it's unclear how to determine which specific client was using which specific device using usbip tools on the server.
I'm not sure if there's a simpler solution available that I'm missing. Perhaps there's a configuration setting or a different approach that would solve this more elegantly?

[seastwood]

Yeah, I agree it's a critical problem. I made a USBIP Client Linux GUI and the way I handle this issue is by using ssh connections to automate binding/unbinding when attaching a device. Any time a device is attached through the GUI it does an unbind first, then binds, then, attaches. No need to manually touch the server side terminal. It's a work in progress, but that's I how I personally dealt with it. Perhaps the Windows client could implement something like this as well.

[seastwood]

The nice thing about the ssh connection method is you can also set it up to automatically fetch all the devices that can be attached, so all you need to do is double click one and boom it's attached. It acts a lot like VirtualHere in that sense. It's not very hard to implement.

[Andreyokey]

#109 (comment) The problem was solved by slightly correcting the usbipd sources, thanks to vadimgrn advice

[seastwood]

Nice! I'm glad that exists for the server side. It seems like something that should be easier to modify.