On Tue, Jun 23, 2009 at 8:18 PM, Thomas A. Moulton<t...@moulton.us> wrote: >> All is not rosy and perfect, "WinUSB" would require an INF file that >> *points* to the driver - much like the work that Freddy is working >> towards with a universal libusb inf file >> > > This is a VERY interesting suggestion. > > WunUSB *is* a system library, as it comes from the OS vendor and > provides general services for many devices, not just one subset of > devices. It is a General USB interface. > > This should also have the advantage of being signed by microsoft so it > will install on all (current) versions of the windows operating systems. > > The question I have is... > > If we have an INF file pointing to a signed driver, does the INF/Driver > pair need to be signed, or is the signing just the authenticate the > driver CODE as being trusted? > > If it is just the driver code, then I think this is the most stable long > term solution above all.
The WinUSB driver is signed. You can load the driver with an INF file. It is not WHQL so there will be a warning message. The KMCS paper is worth reading. http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/kmsigning.doc This is the thread last time in libusb-win32. http://www.nabble.com/Win-Vista-32-64-Build.-td17313102.html -- Xiaofan http://mcuee.blogspot.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
