From: Earnie <ea...@us...> - 2011-06-04 15:32:33
|
Xiaofan Chen wrote: > On Sat, Jun 4, 2011 at 1:55 AM, Charles Wilson > <cwi...@us...> wrote: >> This is mainly intended for Xiaofan Chen... >> >> I see that the libusb-w32 project distributes a digitally signed kernel >> mode driver. I would like to add, to the MinGW distribution, the >> following driver: >> >> http://mingw.cwilson.fastmail.fm/QueueUserAPCEx-install.exe >> >> That's an installer for alertdrv.sys, documented here: >> >> http://www.codeproject.com/KB/threads/queueuserapcex.aspx >> http://www.codeproject.com/KB/threads/QueueUserAPCEx_v2.aspx >> http://mingw.cwilson.fastmail.fm/QueueUserAPCEx-install.RELEASE_NOTES.txt >> >> This driver can be used, optionally, by the GCE version of Pthreads-W32 >> (that is, the "C++ cleanup" version of Pthreads-W32). >> >> However, at present the compiled driver is unsigned, so it can't be used >> by W7-64 or Windows Server 2008-64 (dunno about -32 variants). > > It should be fine for 32 bit Windows OS. Windows Vista 64bit > onwards require KMCS: Vista 64, Windows Server 2008 64bit, > Windows 7 64bit and Windows Server 2008 R2 64bit require > KMCS. > Is this true even for 32bit binaries? >> How difficult is it to sign a driver? How did you guys go about getting >> the necessary certifications in order to be able TO sign your driver? >> What's the process? Does it cost anything? >> > > It is not difficult but it costs money. We get donations to pay for the > digital certificates. The easiest is to get the Personal Certificates > from GlobalSign. The other alternative is VeriSign. Both have the > US$99 for one year promotion now. > http://www.globalsign.com/code-signing/code-signing-for-individual-developers.html > (we got the 3-year package for US$244 this year). > https://winqual.microsoft.com/help/why_is_a_digital_certificate_required_for_winqual_membership.htm > I'm guessing that our cloud host can provide us one, I'll ask them. > The full list of accepted signing authority is here. In the end, > only GlobalSign and VeriSign are real choices as others > have been absorbed. > http://msdn.microsoft.com/en-us/windows/hardware/gg487315 > > The process is documented here in detail and not that difficult > to follow. You need to have WDK installed. > http://msdn.microsoft.com/en-us/windows/hardware/gg487328 > > Luckily I think now you have an alternative choice provided > by ReactOS. As long as your driver is fulfilling their conditions, > it should be okay. > http://www.reactos.com/wiki/Driver_Signing > > This phrase "A link back to the ReactOS homepage somewhere on the project/product's page. Preferably someplace that is easily sighted." prevents us from using it. It also goes against the GPL and FDL they use for their software and documentation. -- Earnie -- http://www.for-my-kids.com |