Re: Libusbk for Window 10 signing

Børge Strand-Bergesen <[email protected]> Mon, 10 Aug 2015 10:34:27 +0200
Newsgroups gmane.comp.lib.libusb.devel.windows
Message-ID <CAE9Na6Ha1jEi2GsqeLgey0U59Wh5WCQMQN_X9hzLiQigpRDw9A@mail.gmail.com>
Hi Xiaofan,

I'm part of the open source Audio Widget project and the owner of one
commercial hardware implementation of it.

We have a Windows driver based on libusbK (.sys and .dll), and I'd
like it to continue working for still some time. As an embedded
hardware guy I don't personally have the skill to port the driver to
another library.

Does this mean the existing built driver will not install / eventually
stop working / work forever on Win10? Which one applies to a
libusbk.dll based driver built in the future? It's important that I
warn existing users about any driver updates.

The ideal would of course be that the existing driver installs forever
on all of Win7/8/10, but bar that, I hope a new build can still
install on all three.

If this is a matter of funding a certificate for libusbK, let me know.


All the best,
Borge





On Mon, Aug 10, 2015 at 10:12 AM, Xiaofan Chen <[email protected]> wrote:
> On Fri, Aug 7, 2015 at 4:39 AM, michel <[email protected]> wrote:
>> if i  get it right today libusbk driver should work fine with win-10 as part
>> of MS migration plan
>> old signed driver signed  before win10 will pass win10 signing check .
>>
>> Does anybodies here has any plan or could get a rebuilt libusbk driver
>> resigned for win 10 ?
>> i  can of understand they migth be a 90 day periof where this could be done
>> free
>> but  what  passed  that  fatal 90 day period ?
>>
>> see
>> http://blogs.msdn.com/b/windows_hardware_certification/archive/2015/04/01/driver-signing-changes-in-windows-10.aspx
>>
>
> It is quite complicated and some of the things mentioned in the above
> blog is not correct.
>
> Ref:
> https://www.osronline.com/showthread.cfm?link=268241
>
> I did not read all the messages in that thread. But it seems
> to me the old cross certificate will still work until June 2016.
>
> On the other hand, you need a new EV certificate to sign
> for Windows 10. I am not so sure if anyone here can get
> hold of an EV certificate and is willing to sign the driver
> and release to the public.
>
> I tend to think this is really the end of libusbK driver. And
> on the other hand, you can use WinUSB driver.
>
> --
> Xiaofan
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Libusb-win32-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/libusb-win32-devel

------------------------------------------------------------------------------