The Trusted Publishers certificate store contains information about the Authenticode (signing) certificates of trusted publishers that are installed on a computer. In order to test and debug your driver packages within your organization, your company should install the Authenticode certificates that are used to sign driver packages in the Trusted Publishers certificate store. Install the Authenticode certificates on each computer in the workgroup or organizational unit that runs signed code. The name of the Trusted Publishers certificate store is trustedpublisher.
If a publisher's Authenticode certificate is in the Trusted Publishers certificate store, Windows installs a driver package that was digitally signed by the certificate without prompting the user (silent install). By installing the Authenticode certificates in the Trusted Publishers certificate store, you can automate the installation of your driver package on various systems that are used for internal testing and debugging.
Important This practice of automating the installation of driver packages is only suggested for your internal systems. This practice should never be followed for any driver package that is distributed outside your organization.
The Trusted Publishers certificate store differs from the Trusted Root Certification Authorities certificate store in that only end-entity certificates can be trusted. For example, if an Authenticode certificate from a CA was used to test-sign a driver package, adding that certificate to the Trusted Publishers certificate store does not configure all certificates that this CA issued as trusted. Each certificate must be added separately to the Trusted Publishers certificate store.
Use a Group Policy to distribute certificates to an organizational unit on a network. In this situation, the administrator adds a Certificate Rule to a Group Policy to establish trust in a publisher. Certificate Rules are part of the software restriction policies that are supported on the following Windows versions:
Windows Vista and later versions of Windows.
Windows Server 2003.
You can manually install the Authenticode certificates into the Trusted Publishers certificate store on a computer by using the CertMgr tool.
Note The driver signing verification policy used by Plug and Play requires that the Authenticode certificate of a CA has been previously installed in the local machine version of the Trusted Publishers certificate store. For more information, see Local Machine and Current User Certificate Stores.
For more information about software restriction policies and using Certificate Rules, see the information in the Windows Help and Support Center. In addition, you find more information about these topics on the Microsoft TechNet website.
For more information about how to deploy Authenticode certificates in an enterprise by using Group Policy, see the readme file Selfsign_readme.htm, which is located in the src\general\build\driversigning directory of the WDK.
For more information about certificate stores, see the Code Signing Best Practices website.