我应该更喜欢哪一个，普通的还是 EV 代码签名证书？
Which one should I prefer, regular or EV code signing certificate?
我想签署我的驱动程序，我查看了 MSDN，看到了这个：https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/get-a-code-signing-certificate
他们说：
If you don’t have an approved EV code signing certificate, you can buy one from one of the certificate authorities below.
这是否意味着我应该只购买 EV 代码签名证书来签署我的驱动程序，或者普通的也足够了？ bad/good 边是什么？谢谢
是您需要EV证书，如您分享的link所述：
Microsoft requires an extended validation (EV) code signing certificates from partners enrolled and authorized for Kernel Mode Code Signing as part of the Microsoft Trusted Root Certificate Program.
Tim Roberts 社交 MSDN 上的回答可能会阐明该过程：
You can get Microsoft's signature in two ways: by running the WHQL tests and submitting the test results, or by submitting your driver package for attestation signing. Both of those things require that you submit your driver through the "developer hardware dashboard". The problem is that creating a "developer hardware dashboard" account requires an EV certificate.
我想签署我的驱动程序，我查看了 MSDN，看到了这个：https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/get-a-code-signing-certificate
他们说：
If you don’t have an approved EV code signing certificate, you can buy one from one of the certificate authorities below.
这是否意味着我应该只购买 EV 代码签名证书来签署我的驱动程序，或者普通的也足够了？ bad/good 边是什么？谢谢
是您需要EV证书，如您分享的link所述：
Microsoft requires an extended validation (EV) code signing certificates from partners enrolled and authorized for Kernel Mode Code Signing as part of the Microsoft Trusted Root Certificate Program.
Tim Roberts 社交 MSDN 上的回答可能会阐明该过程：
You can get Microsoft's signature in two ways: by running the WHQL tests and submitting the test results, or by submitting your driver package for attestation signing. Both of those things require that you submit your driver through the "developer hardware dashboard". The problem is that creating a "developer hardware dashboard" account requires an EV certificate.