Cert used to sign DTM required test driver is expired?

NTDEV
1

All,

Has anyone else noticed that the DTM 1.5 nmpcl60.sys driver file ( the
virtual network interface used to test LWF drivers ) was signed with a
cert that expired back in 06/16/2010? The only way I can get it to load
is to re-sign it using my own cert. Makes it difficult to run DTM tests
on 64bit OSs that will refuse to load drivers without proper sigs. I’m
wondering if anyone else has a better way around this.

-Matthew

2

> All,

Has anyone else noticed that the DTM 1.5 nmpcl60.sys driver file ( the
virtual network interface used to test LWF drivers ) was signed with a
cert that expired back in 06/16/2010? The only way I can get it to
load
is to re-sign it using my own cert. Makes it difficult to run DTM
tests
on 64bit OSs that will refuse to load drivers without proper sigs. I’m
wondering if anyone else has a better way around this.

Can windows be fooled by setting the system date?

I’m surprised that the signing wasn’t timestamped though…

James

3

On 12/17/2010 8:07 PM, James Harper wrote:

Can windows be fooled by setting the system date?

I’m surprised that the signing wasn’t timestamped though…

I did try that, but other things broke as a result.

-Matthew