How to put an unsigned driver get on a 64-bit OS? Thought this might be of
interest to folks here.
http://blogs.msdn.com/windowsvistasecurity/archive/2007/08/03/x64-driver-sig
ning-update.aspx
I’m actually kind of interested into why *VeriSign* pulled their cert. I can certainly understand Microsoft revoking it from their own internal lists, that’s their own perogative of course.
But I am curious as to what VeriSign policy VeriSign is saying that was broken to justify the code signing cert being revoked [by VeriSign]. That seems fishily like VeriSign saying “we’ll revoke A customer’s cert on B customer’s word”, which seems pretty broken in principle to me - one customer’s policies can be completely arbitrary, and “X other VeriSign customer broke my terms of use!” would not appear to be a very sound reason for a trusted root CA to be arbitrarily revoking certs.
Of course, this is just speculation on my part based on a lack of information from VeriSign, but again, I’d be very interested to hear the rationale behind the underlying code signing cert being revoked by the root CA.
–
Ken Johnson (Skywing)
Windows SDK MVP
http://www.nynaeve.net
“Timothy R. Mangan” wrote in message news:xxxxx@windbg…
How to put an unsigned driver get on a 64-bit OS? Thought this might be of interest to folks here.
http://blogs.msdn.com/windowsvistasecurity/archive/2007/08/03/x64-driver-signing-update.aspx