Changes between Version 35 and Version 36 of BuildingTapWindows6

Timestamp:

04/05/19 08:34:18 (3 years ago)

Author:

Samuli Seppänen

Comment:

Add preliminary attestation signing instructions

BuildingTapWindows6

@@ -74 +74 @@
 = Building and signing for Windows 10 =
 
-On top of the generic requirements listed above you will have to register you EV dongle with your organization's account in the Windows Dev Center ([https://developer.microsoft.com/en-us/dashboard/account/managecertificates link]).
+On top of the generic requirements listed above there are a few extra requirements when doing attestation signing:
+
+* You need to register your EV dongle with your organization's account in the Windows Dev Center ([https://developer.microsoft.com/en-us/dashboard/account/managecertificates direct link]).
+* INF file syntax needs to be valid, as MS backend servers will check it at submission time. Use the latest version of !InfVerif (see footer in Hardware Dev Center) to validate the syntax before submission.
 
 The building and signing process is as follows
@@ -96 +99 @@
 }}}
 
-Now generate a catalog file as described [here https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/attestation-signing-a-kernel-driver-for-public-release], sign it with signtool.exe using the EV dongle and submit via Windows Dev Center for attestation signing.
+The next steps are
+* Generate a cabinet file as described [https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/attestation-signing-a-kernel-driver-for-public-release here].
+  * ''You have to'' put the driver files into one or more directories in the cabinet file as shown in the example diagram [https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/attestation-signing-a-kernel-driver-for-public-release here]. If you don't, cabinet file verification will fail.
+* Sign the cabinet file with the EV dongle using signtool.exe
+* Submit the cabinet file to Windows Dev Center to obtain an attestation signature
 
 = Useful commands =