Context Navigation

Changes between Initial Version and Version 1 of Ticket #13882, comment 1

initial	v1
1	1	Three is nothing wrong here, you're just confused by the log file.
2		"supR3HardNtViCallWinVerifyTrustCatFile -> 0 (was CERT_E_CHAINING)" overrides the previous "supR3HardNtViCallWinVerifyTrust: WinVerifyTrust failed with 0x800b010a (CERT_E_CHAINING) on ..." message in every case. That is to say, we've used an alternative way of checking the authenticity of the DLLs via windows APIs. (This DLL and it's signature was already checked out by our own signature verification code.)
	2	"supR3HardNtViCallWinVerifyTrustCatFile -> 0 (was CERT_E_CHAINING)" overrides the previous "supR3HardNtViCallWinVerifyTrust: WinVerifyTrust failed with 0x800b010a (CERT_E_CHAINING) on ..." message in every case. That is to say, we've used an alternative way of checking the authenticity of the DLLs via windows APIs. (This DLL and its signature was already checked out by our own signature verification code.)
3	3
4	4	Btw. the NVIDIA DLLs aren't self signed, they have a sub CA certificate "CN=NVIDIA Subordinate CA 2014, DC=nvidia, DC=com" issued to them by "CN=Microsoft Digital Media Authority 2005". This microsoft root CA certificate isn't found by the WinVerifyTrust API and it thus returns CERT_E_CHAINING as it cannot anchor the trust chain. Microsoft doesn't appear to install this certificate as a trusted root certificate by default, they probably have a reason for this, though it escapes me. Both AMD/ATI and Intel have similar subordinate CA certificates, btw.