Re: Libusbk for Window 10 signing
Travis <[email protected]> Mon, 10 Aug 2015 08:58:06 -0600
| Newsgroups | gmane.comp.lib.libusb.devel.windows |
|---|---|
| Message-ID | <[email protected]> |
Greetings, LibusbK is already signed with a DigiCert High Assurance EV Root CA. At some point, I would like to add the WinUSB ISO support to the libusbK library and let it become our "primary" driver. There is little advantage to using libusbK.sys compares to the newer WinUsb.sys with ISO support. That said, nothing is going to stop working. Even if we support WinUSB ISO, we will not throw libusbK.sys away. I would expect most all users to WANT to transition to the winusb driver. There are some big advantage because it is essentially a built-in windows driver for custom usb devices. You can even add things to you USB descriptor which identifies it as a "winusb" device and eliminate the need for a driver installer all-together. Regards, Travis On 8/10/2015 7:30 AM, Xiaofan Chen wrote: > On Mon, Aug 10, 2015 at 9:27 PM, Børge Strand-Bergesen > <[email protected]> wrote: >> Thank you! >> >> I can live very well with libusbK, and have done for quite some >> time now :-) >> >> Does this mean lubusbk.sys signed with a non-EV certificate will >> function and install after June 2016, and that new builds of it will >> need an EV certificate? > Yes. The new builds for Windows 10 will require an EV certificate. > New builds for Windows XP/Vista/7 do not need an EV certificate. > >> Sorry for going on about this, I just wish to know how these things >> are connected and how it influences the stuff I ship. >> (www.henryaudio.com) > No problem. > > ------------------------------------------------------------------------------ _______________________________________________ Libusb-win32-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel