| 
      
      
      From: Spiro T. <an-...@sp...> - 2007-11-11 09:51:03
      
     | 
| Hello Paarvai, * On Sat, Nov 10, 2007 at 11:01:17AM -0800 Paarvai Naai wrote: > The > impression I had was that Microsoft wants to keep the kernel mode code > signing (KMCS) separate from WHQL. The INF gets signed and hashed as > part of the WHQL process. Indeed, you are right. I confused all of this. > There is discussion in the kmsigning.doc that specifically says that > you can release a driver *without* WHQL as long as you follow KMCS. Yes, I was aware of this, but I totally forgot that signing the INF is part of WHQL, not of KMCS. > Sprio, did you look through that document above and find something > contradictory, or are you working of some other reference? I have had a look into that document more than once, but not recently. What I had written was from my memory, and it seems I was confused "a little bit". So, please disregard my previous statements. > Personally, I'm unclear on all of this and Microsoft's documentation > hasn't been the greatest here. Sadly, the only way to really be sure > would be to try this all out or here from someone who has. We could ask this question on the MS newsgroups; questions regarding signing are rather common there. It might be better to search for something there, as there have been many questions regarding this. However, even if this is possible: We would still need someone who is willing to sign the driver. BTW: I have another driver project (http://sf.net/projects/opencbm) where I would want at least the 64 bit driver to be signed. ;) Gruß, Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ |