Windows XP 32 位的设备驱动程序代码签名
我已经为设备编写了设备驱动程序，但每次在 Windows XP 32 位中连接设备时，都会出现“发现新硬件”向导。
我使用 Comodo 代码签名证书对驱动程序进行签名，而不是使用交叉证书链链接到 Microsoft 根权限。驱动程序 wql 也未经过认证。
所以我的问题是禁用 Windows XP 上的发现新硬件向导：
i) 我的驱动程序需要经过 wql 认证吗？
ii) 使用 verisign 的交叉证书与 Microsoft 根证书进行签名？
iii）或者我在代码中遗漏了一些需要更改的内容？
I have written a device driver for a device but each time I connect the device in windows XP 32 bit, "found new hardware" wizard appears.
I am signing the driver using a Comodo code signing certificate and not using the cross certificate chain to link to microsoft root authority. Nor is the driver wql certified.
So my question is to disable the found new hardware wizard on windows xp:
i) Does my driver needs to be wql certified?
ii) signed with microsoft root certificate using cross certificate from verisign?
iii) or something i missed out in my code which needs to be changed?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
做了一些研究并找到了答案：
Windows XP 不支持authenticode 驱动程序签名，并且没有计划添加它。唯一的方法是使用交叉证书使用微软证书进行签名
did some research and found the answer:
windows XP does not support authenticode driver signing and there are no plans to add it. Only way is to sign using microsoft certificate by using a cross certificate
据我所知，Windows XP 唯一识别的驱动程序签名是 WHQL 签名。交叉签名与此无关。 （交叉签名允许 Windows Vista 内核驱动程序加载程序识别 Authenticode 签名。它与 Windows XP 驱动程序加载无关。）
Authenticode 签名虽然可以使用 DIFx / DpInst 进行验证，但稍后当 SetupAPI 尝试安装时将无法验证您的设备驱动程序已从驱动程序存储中删除。
As far as I know, the only driver signing recognized by Windows XP is a WHQL signature. Cross-signing has nothing to do with it. (Cross-signing allows the Windows Vista kernel driver loader to recognize Authenticode signatures. It has nothing to do with Windows XP driver loading.)
Authenticode signatures, while they would validate with DIFx / DpInst, would fail to validate later when SetupAPI tries to install your device driver out of the driver store.