Re: [Libusb-win32-devel] Antwort: 64-bit support

[Paarvai N. <ope...@gm...>]

Hi Stephan,

Thanks for the quick reply.  My response below:

On Nov 9, 2007 1:49 AM, Stephan Meyer <Ste...@ia...> wrote:
> * install the latest DDK
> * open a DDK 64bit build environment

Does this have to be the Windows Server 2003 SP1 DDK or can it be the
latest WDK?


> Yes you can. Just copy the 32bit DLL to Windows' 'syswow64' folder.

Does the 32-bit DLL have to be built with the DDK or will the MinGW
version work?  I am guessing that the MinGW one will work too.


> It's not possible to sign just a driver (.sys file).
> You always have to sign the combination of the driver and the device
> specific .inf file.

Actually it is my understanding that you have to have a signed CAT
file but the CAT file does not need to have hashes for anything but
the KMOD (.sys file) to pass through the Kernel Mode Code Signing
(KMCS) requirements.  Please see:

http://download.microsoft.com/download/d/c/3/dc32d46e-58e7-46b8-8689-a3b17606b53a/kernel_mode_code_signing_x-64_windows_vista.ppt
http://www.microsoft.com/whdc/winlogo/drvsign/kmsigning.mspx
http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/kmsigning.doc

This makes sense anyway since if one were to use winusb.sys, they
don't need to sign their INF and DLL (unless they wish to have WHQL
certification).  In the same way, if a publisher makes a SYS, DLL, and
INF file, they would simply have to sign the SYS file and the
situation would be then similar to using a 3rd party SYS file.

I know that using winusb.sys is probably the best long-term approach,
but having an official libusb-win32 signed driver seems like a great
short-term stop gap.  I am not totally sure, but I believe our company
would be willing to sponsor the cost of a Verisign certificate in that
case.

Best regards,
Paarvai