Attestation signing a kernel driver for public release
This topic describes how to sign a driver using attestation signing.
Attestation signing has the following properties.
- Attestation signing supports Windows 10 Desktop kernel mode and user mode drivers. Although user mode drivers do not need to be signed by Microsoft for Windows 10, the same attestation process can be used for both user and kernel mode drivers.
- Attestation signing requires the use of an EV Certificate to submit the driver to the Hardware Dev Center (Sysdev) dashboard.
- An attestation signed driver will only work for Windows 10 Desktop. It will not work for other versions of Windows, such as Windows Server 2016,Windows 8.1, or Windows 7.
- Attestation signing requires driver folder names to contain no special characters, and to be less than 40 characters long.
Attestation Signing a Kernel Mode Driver
To attestation sign a kernel mode driver complete the following steps:
- Acquire an EV Code Signing Certificate
- Register your company for the Hardware Dev Center (Sysdev)
- Download and install the Windows Driver Kit
- Create a CAB files submission
- Sign the CAB file submission with your EV Cert
- Submit the EV signed Cab file using the Hardware Dev Center (Sysdev) dashboard
- Validate that the driver was properly signed
- Test your driver on Windows 10 for Desktop
Acquire an EV Code Signing Certificate
Before you can submit binaries files using the dashboard to be signed, you need to acquire an extended validation (EV) code signing certificate to secure your digital information. This certificate is the accepted standard for establishing your company's ownership of the code you submit. It allows you to digitally sign PE binaries, such as .exe, .cab, .dll, .ocx, .msi, .xpi and .xap files.
Follow the process described in Get a code signing certificate to acquire the needed EV code signing certificate.
Register your company for Hardware Dev Center (Sysdev) Dashboard Services
You can sign your drivers using the legacy (Sysdev) dashboard. To access the Sysdev dashboard, you'll need to register your company and get a code signing certificate.
Follow the process described in Before You Sign In to set up the account you will need on the dashboard.
Download and install the Windows Driver Kit
You will need to download and install the Windows Driver Kit (WDK) to gain access to tools that are used to sign binary files.
Follow the process described in Download kits and tools for Windows 10 to download and install the WDK.
Create a CAB Files Submission
To create a CAB files submission for the dashboard, complete the following steps.
- Gather the binaries that you will submit to be signed in a single directory. In this example, we will use C:\Echo. The steps described here, will reference the echo driver available in GitHub at this location
Typical cab file submissions contain the following.
- The driver itself, for example Echo.sys
- The driver INF file that is used by the dashboard to facilitate the signing process.
- The symbol file that is used for debugging information. For example, Echo.pdb.
- Catalog .CAT files are not required. Microsoft regenerates catalog files and replaces any catalog files that were submitted.
- Use MakeCab.exe to process the DDF file and create a cab file.
Open a Command Prompt window as Administrator. Then enter the following command to view the MakeCab options:
C:\Echo> MakeCab /? Cabinet Maker - Lossless Data Compression Tool MAKECAB [/V[n]] [/D var=value ...] [/L dir] source [destination] MAKECAB [/V[n]] [/D var=value ...] /F directive_file [...] source File to compress. destination File name to give compressed file. If omitted, the last character of the source file name is replaced with an underscore (_) and used as the destination. /F directives A file with MakeCAB directives (may be repeated). Refer to Microsoft Cabinet SDK for information on directive_file. /D var=value Defines variable with specified value. /L dir Location to place destination (default is current directory). /V[n] Verbosity level (1..3).
- Prepare a cab file DDF input file. For our Echo driver it might look something like this.
;*** Echo.ddf example ; .OPTION EXPLICIT ; Generate errors .Set CabinetFileCountThreshold=0 .Set FolderFileCountThreshold=0 .Set FolderSizeThreshold=0 .Set MaxCabinetSize=0 .Set MaxDiskFileCount=0 .Set MaxDiskSize=0 .Set CompressionType=MSZIP .Set Cabinet=on .Set Compress=on ;Specify file name for new cab file .Set CabinetNameTemplate=Echo.cab ; Specify the subdirectory for the files. ; Your cab file should not have files at the root level, ; and each driver package must be in a separate subfolder. .Set DestinationDir=Echo ;Specify files to be included in cab file C:\Echo\Echo.Inf C:\Echo\Echo.Sys
Note All driver folders in your cab must support the same set of architectures, for example, all drivers must be x86 or all drivers must be x64, or all drivers must support both x86 and x64.
- Call the makecab utility and provide the ddf file as input using the /f option.
C:\Echo> MakeCab /f "C:\Echo\Echo.ddf
The output of makecab should display the number of files in the created cabinet, in our example 2.
C:\Echo> MakeCab /f Echo.ddf Cabinet Maker - Lossless Data Compression Tool 17,682 bytes in 2 files Total files: 2 Bytes before: 17,682 Bytes after: 7,374 After/Before: 41.70% compression Time: 0.20 seconds ( 0 hr 0 min 0.20 sec) Throughput: 86.77 Kb/second
- Locate the cab file in the Disk1 subdirectory. You can click the cab file in File Explorer to verify that it contains the expected files.
Sign the Submission Cab File with your EV Cert
- Use the process recommended by the EV cert provider to sign the cab file with your EV cert. For example, you might use the signtool and if you are using Verisign, you might specify their timestamp server.
C:\Echo> SignTool sign /v /ac "C:\MyEVCert.cer" /s MY /n "Company Name" /t http://timestamp.verisign.com/scripts/timstamp.dll "C:\Echo\Disk1\Echo.cab"
Note Use industry best practices to manage the security of the EV cert signing process.
Submit the EV signed Cab file using the Hardware Dev Center (Sysdev) dashboard
- Submit the EV signed Cab file using the Hardware Dev Center (Sysdev) dashboard For more information see Driver Signing Properties and File Signing Services.
As part of the submission process you will indicate what architectures all of the drivers in the submission support. Three options are available using the check boxes.
- x86 and x64
All driver folders in your cab must support the same set of architectures, for example, all drivers must be x86 or all drivers must be x64 or support both x86 and x64. If you have drivers that support different combinations of architectures, create separate submissions.
You will also indicate if you are submitting universal drivers. For more information see, Getting Started with Universal Windows drivers.
The following screen shot shows the options for submitting the echo driver for signing.
- When the signing process is complete, download your signed driver from the Sysdev dashboard. ## Validate that the driver was properly signed
Complete the following steps to validate that the driver was properly signed.
After you have downloaded the submission file, extract the driver file.
Open a Command Prompt window as Administrator. Then enter the following command to verify that the driver was signed as expected.
C:\Echo> SignTool verify Echo.Sys
3.To list additional information and have signtool verify all signatures in a file with multiple signatures, type the following.
C:\Echo> SignTool verify /pa /ph /v /d Echo.Sys
- To confirm the EKUs of the driver complete the following steps. a. Open Windows Explorer and locate the binary file. Right-click the file and select Properties. b. On the Digital Signatures tab, select the listed item in the Signature list. c. Select the Details button, and then select View Certificate. d. On the Details tab, select the Enhanced Key Usage field. When the driver is resigned by the dashboard the following process is used.
- Appends a Microsoft SHA2 embedded signature.
- If the driver binaries are embedded signed by the customer with their own certificates, those signatures will not be overwritten.
- Creates and signs a new catalog file with a SHA2 Microsoft certificate. This catalog replaces any existing catalog provided by the customer.
Test your driver on Windows 10 for Desktop
Use the following instructions to install the sample driver.
Open Device Manager, right click on the computer icon and select "Add legacy Hardware". Follow the prompts to complete the install of the driver.
Alternatively, open a Command Prompt window as Administrator and use devcon to install the driver. Navigate to your driver package folder, and enter the following command.
C:\Echo> devcon install echo.inf root\ECHO
- Confirm that the driver install process does not display the "Windows can't verify the publisher of this driver software." Windows security dialog box.
Create a Multiple Driver Submission
To submit multiple drivers at the same time create a sub directory for each driver as shown below.
Prepare a cab file DDF input file that references the subdirectories. It might look something like this.
;*** Submission.ddf multiple driver example ; .OPTION EXPLICIT ; Generate errors .Set CabinetFileCountThreshold=0 .Set FolderFileCountThreshold=0 .Set FolderSizeThreshold=0 .Set MaxCabinetSize=0 .Set MaxDiskFileCount=0 .Set MaxDiskSize=0 .Set CompressionType=MSZIP .Set Cabinet=on .Set Compress=on ;Specify file name for new cab file .Set CabinetNameTemplate=Echo.cab ;Specify files to be included in cab file ; First Driver .Set DestinationDir=DriverPackage1 C:\DriverFiles\DriverPackage1\Driver1.sys C:\DriverFiles\DriverPackage1\Driver1.inf ; Second driver .Set DestinationDir=DriverPackage2 C:\DriverFiles\DriverPackage2\Driver2.sys C:\DriverFiles\DriverPackage2\Driver2.inf
Follow the steps previously described to sign, submit and test the driver files.