Changes between Version 5 and Version 6 of libwdi/signed_driver_walkthrough

Timestamp:

02/08/11 19:42:09 (2 years ago)

Author:

pbatard

Comment:

--

libwdi/signed_driver_walkthrough

@@ -12 +12 @@
  1. The [http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff latest WDK]
 
-For the purpose of this exercise, I will be using libusb-win32_ft2232_driver files from the latest [http://www.freddiechopin.info/index.php/en/download/category/10-openocd-dev OpenOCD-dev 0.5.0] as well as driver signing credentials obtained from !GlobalSign [TODO: detail the files obtained]. The development toolchain will be WDK 7.0.0.
+For the purpose of this exercise, I will be using libusb-win32_ft2232_driver files from the latest [http://www.freddiechopin.info/index.php/en/download/category/10-openocd-dev OpenOCD-dev 0.5.0] as well as driver signing credentials obtained from !GlobalSign (this would be a .pfx, along with the private key password). The development toolchain will be WDK 7.0.0.
 
 == Obtaining a driver signing certificate ==
@@ -191 +191 @@
 == Creating a signed cat file ==
 
-'''Why would one want a signed cat'''
+'''Why would you want a signed cat?'''
 
 What we did above allows the installation of drivers in a Windows environment outside of test mode, which is fine and all, but unless you sign the inf as well, you will get the following prompt on Vista and later versions of Windows during driver installation:
@@ -296 +296 @@
 == Packaging the signed files in libwdi ==
 
+Since we went the trouble of creating a fully signed driver package, that can install without prompts, we might as well deliver the whole thing in a package that is attractive for end users. Also, if you want to avoid the need for users to add your certificate as a Trusted Publisher, libwdi can help you out.
+
 == Installing the certificate as a Trusted Publisher using libwdi ==