Donate Share

libusb-win32

Tracker: Feature Requests

5 Vista 64bit Support - ID: 2816612
Last Update: Comment added ( armyofbile )

Please support 64bit Vista.
The driver compiles, but won't run without a certificate!


Nobody/Anonymous ( nobody ) - 2009-07-04 14:05

5

Open

None

Nobody/Anonymous

None

None

Public


Comments ( 4 )




Date: 2009-10-03 22:02
Sender: armyofbile

http://www.killertechtips.com/2009/05/05/disable-driver-signing-windows-7/


this applies to vista 64 bit as well


Date: 2009-09-15 03:18
Sender: linuxjosef

I found a site describing how to get a driver to work without buying a
certificate, but it doesn't seem to work.
http://www.minasi.com/newsletters/nws0903.htm
I guess you need "Microsoft Code Signing Root" in the path for it to work
:(
http://www.microsoft.com/whdc/driver/tips/IFS_Signing.mspx?pf=true


Date: 2009-09-15 01:56
Sender: linuxjosef

I believe you don't have to sign the .inf file, so a generic driver can b
used as long as you don't have to edit the sourcecode.

Take for example a look at the NVidia Graphics drivers.
They don't release drivers for Notebooks as frequently as the regular ones
and didn't release them at all until recently.
So people were using modified inf files to install them, and they work
fine.

Windows tells you this is not a certified driver while installing, but it
works.

libusb doesn't work at all.

There is no need to certify the driver at MS or anything. You just have to
add a signature with a certificate from a trusted authority (e.g. thawte).

It would be usefull for many open-source projects or people that cannot
afford a certificate.



Date: 2009-07-07 18:30
Sender: nobody

Since you will need to sign your device files (this includes .sys driver,
possibly .dll, .cat catalog file and .inf file ++) that is specific to
your hardware device anyway it does not make much sense for libusb-win32 to
include a set of certified drivers.

If you first have a signed driver for Vista 64 bit, you cannot e.g. change
the USB VID, PID or interface number to use in the .inf device file without
doing a re-certification. It would only make sense to distribute signed
drivers for users who can modify the firmware of their hardware and
replicate (for use internally during development) the VID / PID / Interface
in the pre-certified driver.

You will need to do a Windows driver certification in the end for your
hardware in the end, anyways. I don't think your request will be approved.


Log in to comment.




Attached File

No Files Currently Attached

Change

No changes have been made to this artifact.