windows驱动数字签名

http://msdn.microsoft.com/en-us/library/ff543743%28v=VS.85%29.aspx

 

Digital Signatures

Digital signatures are based on Microsoft public key infrastructure technology, which is based on Microsoft Authenticode combined with an infrastructure of trusted certification authorities (CAs). Authenticode, which is based on industry standards, allows vendors, or software publishers, to sign either a file or a collection of files (such as a driver package) by using a code-signing digital certificate that is issued by a CA.

Windows uses a valid digital signature to verify the following:

• The file, or the collection of files, is signed.

• The signer is trusted.

• The certification authority that authenticated the signer is trusted.

• The collection of files was not altered after it was published.

For example, this signing process for a driver package involves the following:

• A publisher obtains an X.509 digital certificate from a CA. An Authenticode certificate is also referred to as a signing certificate. A signing certificate is a set of data that identifies a publisher, and is issued by a CA only after the CA has verified the identity of the publisher. A CA can be a Microsoft CA, a third-party commercial CA, or an Enterprise CA.

  The signing certificate is used to sign the catalog file of a driver package or to embed a signature in a driver file. Certificates that identify trusted publishers and trusted CAs are installed in certificate stores that are maintained by Windows.

• The signing certificate includes a private key and a public key, which is known as the key pair. The private key is used to sign the catalog file of a driver package or to embed a signature in a driver file. The public key is used to verify the signature of a driver package's catalog file or a signature that is embedded in a driver file.

• To sign a catalog file or to embed a signature in a file, the signing process first generates a cryptographic hash, or thumbprint, of the file. The signing process then encrypts the file thumbprint with a private key and adds the thumbprint to the file.

  The signing process also adds information about the publisher and the CA that issued the signing certificate. The digital signature is added to the file in a section of the file that is not processed when the file thumbprint is generated.

• To verify the digital signature of a file, Windows extracts the information about the publisher and the CA and uses the public key to decrypt the encrypted file thumbprint.

  Windows accepts the integrity of the file and the authenticity of the publisher only if the following are true:

  • The decrypted thumbprint matches the thumbprint of the file.
  • The certificate of the publisher is installed in the Trusted Publishers certificate store.
  • The root certificate of the CA that issued the publisher's certificate is installed in the Trusted Root Certification Authorities certificate store.

For more information about how the Plug and Play (PnP) device installation uses the digital signature of a driver package's catalog file, see Digital Signatures and PnP Device Installation.

For more information about Microsoft public key infrastructure technology, code signing, and digital signatures, see Introduction to Code Signing and Code Signing Best Practices.