Lame certification question

Hi all
We went through the HCK process for our file system minifilter driver and were rewarded with a signed CAT file. But the driver itself was never modified or signed by Microsoft.

We don’t install via the INF file (and in fact only created one solely for the submission) and as I understand it, there is no requirement for a file system filter driver to do so.

The next step is to certify the product that uses our driver. According to the document at https://msdn.microsoft.com/en-us/windows/desktop/dn385721.aspx?f=255&MSPPError=-2147217396#digitally_signed_file_test however, it appears that the driver must be signed by Microsoft. Is this still correct and if so, what do we need to do in order to obtain a signed driver?

Regards

Mark

>what do we need to do in order to obtain a signed driver?

MS would never touch your driver binary. You need to install the CAT file to
appear your driver signed by MS. Install your files as you used to do and
then call dpinst(64).exe to register the CAT file. You probably need command
line switch /f

wrote news:xxxxx@ntfsd…

Hi all
We went through the HCK process for our file system minifilter driver and
were rewarded with a signed CAT file. But the driver itself was never
modified or signed by Microsoft.

We don’t install via the INF file (and in fact only created one solely for
the submission) and as I understand it, there is no requirement for a file
system filter driver to do so.

The next step is to certify the product that uses our driver. According to
the document at
https://msdn.microsoft.com/en-us/windows/desktop/dn385721.aspx?f=255&MSPPError=-2147217396#digitally_signed_file_test
however, it appears that the driver must be signed by Microsoft. Is this
still correct and if so, what do we need to do in order to obtain a signed
driver?

Regards

Mark

Hi Frank
many thanks for the clarity. Much appreciated.

Regards

Mark