Apply signed driver
in [Device Drivers]
|
From: Peter on 28 Jun 2010 04:56 Hi, We are a manufacturer of a USB device. The chipset supplier CANNOT provide a signed driver for 64-bit OS. It is unsigned . Actually, the driver is not writte by us. Our boss want me to get a signed driver. We want just get a signed driver for Vista 64-bit and Windows 7 64-bit only. I am a newbie about signed driver. 1. Does anyone give me details steps for applying signed driver ? 2. WHQL is much difficult for us to get it pass since we do not source code for the driver. Am I correct ? 3. Does signed driver show our company name ? Some our customers may not happy since they sell our product under their brand name. Thanks
From: Maxim S. Shatskih on 28 Jun 2010 13:48 > 1. Does anyone give me details steps for applying signed driver ? The company should get a Verisign cert, then apply "signtool" to sign the .sys and/or .cat files. WHQL is not mandatory. It is only useful for a) PnP-installed drivers with INF files AND b) if you cannot afford the "Do you trust this software?" warning on install. > 3. Does signed driver show our company name ? Some our customers may not > happy since they sell our product under their brand name. Then let them sign themselves. -- Maxim S. Shatskih Windows DDK MVP maxim(a)storagecraft.com http://www.storagecraft.com
From: Doron Holan [MSFT] on 28 Jun 2010 13:51 you need the company which created the driver to get it signed. "Peter" wrote in message news:16F47EBE-B451-4E4A-9744-EF2C56081A76(a)microsoft.com... Hi, We are a manufacturer of a USB device. The chipset supplier CANNOT provide a signed driver for 64-bit OS. It is unsigned . Actually, the driver is not writte by us. Our boss want me to get a signed driver. We want just get a signed driver for Vista 64-bit and Windows 7 64-bit only. I am a newbie about signed driver. 1. Does anyone give me details steps for applying signed driver ? 2. WHQL is much difficult for us to get it pass since we do not source code for the driver. Am I correct ? 3. Does signed driver show our company name ? Some our customers may not happy since they sell our product under their brand name. Thanks
From: David Craig on 28 Jun 2010 18:15 Since the OP is not threaded with this response I am only guessing at some of the questions, but from what I have seen in a couple of companies may answer some questions. If the driver is created, compiled, and linked by your company, then you need a VeriSign cert suitable for code signing and the Microsoft cross certificate for VeriSign. Alternatives exist but why bother? If a customer wants a driver tailored to their name they have one choice and it is for them to take your driver that is not signed and do the signing themselves which would make them legally liable and sounds a little crazy. Your company can compile your driver with their name of choice if only the visible properties is of primary importance, but the signatures would all refer to your company. You would do this with a different .RC file specifically for each customer who wants it. Most customers who sell want WHQL just so if they sell to an OEM of computer systems that OEM can use the Windows Logo on the system. I have seen this considered far more important than just the code signing. The multiple drivers will cost your company additional fees for each package and OS, so you need to include those costs as well as the time and costs involved in running additional DTM runs. Also always sign the sys file before the cat file. I think most things ignore the signatures, but why take chances. I also think that signing each driver is wise even if it is not a boot start driver and the WHQL guidelines recommend that you do so even if they don't make it mandatory. "Maxim S. Shatskih" <maxim(a)storagecraft.com.no.spam> wrote in message news:uMLRQouFLHA.4060(a)TK2MSFTNGP04.phx.gbl... >> 1. Does anyone give me details steps for applying signed driver ? > > The company should get a Verisign cert, then apply "signtool" to sign the > .sys and/or .cat files. > > WHQL is not mandatory. It is only useful for a) PnP-installed drivers with > INF files AND b) if you cannot afford the "Do you trust this software?" > warning on install. > >> 3. Does signed driver show our company name ? Some our customers may not >> happy since they sell our product under their brand name. > > Then let them sign themselves. > > -- > Maxim S. Shatskih > Windows DDK MVP > maxim(a)storagecraft.com > http://www.storagecraft.com >
From: Peter on 28 Jun 2010 21:04 Thanks for reply ! It is a USB device. So, it is a PnP device. That is we need to apply WHQL. But we do not want to get WHQL for PC application software and hardware . Only signed driver is needed. 1. Can we apply WHQL for signed driver only ? 2. Can we apply WHQL for only Vista 64-bit and Win7 64-bit ? 3. What is the cost for applying WHQL ? Thanks ! "Maxim S. Shatskih" <maxim(a)storagecraft.com.no.spam> ���g��l��s�D:uMLRQouFLHA.4060(a)TK2MSFTNGP04.phx.gbl... > 1. Does anyone give me details steps for applying signed driver ? The company should get a Verisign cert, then apply "signtool" to sign the ..sys and/or .cat files. WHQL is not mandatory. It is only useful for a) PnP-installed drivers with INF files AND b) if you cannot afford the "Do you trust this software?" warning on install. > 3. Does signed driver show our company name ? Some our customers may not > happy since they sell our product under their brand name. Then let them sign themselves. -- Maxim S. Shatskih Windows DDK MVP maxim(a)storagecraft.com http://www.storagecraft.com
|
Pages: 1 Prev: How to get USB HID Interrupt ? Next: debug print in scsi miniport driver |