Changes between Version 11 and Version 12 of BuildingTapWindows6
- Timestamp:
- 04/21/16 19:25:40 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BuildingTapWindows6
v11 v12 1 [[TOC(inline, depth=1)]] 2 1 3 = Introduction = 2 4 … … 4 6 5 7 = Codesigning = 8 9 == Basic process == 6 10 7 11 Getting the [https://msdn.microsoft.com/en-us/library/windows/hardware/ff686697%28v=vs.85%29.aspx Authenticode signatures] right so that all Windows versions detect them can be quite tricky. This seems to be particularly true for kernel-mode driver packages. In practice tap-windows6 driver needs two signatures: … … 35 39 If this process sounds complicated, it's because it is. At some point would make sense to adapt buildtap.py to add both signatures automatically, which would simplify the process dramatically. However, that would require porting buildtap.py to Windows Kit 10, which would require a non-trivial amount of work. 36 40 37 == Installing certificates == 41 == Useful commands == 42 43 === Installing certificates === 38 44 39 45 Installing a PFX file to the Currentuser certificate store using Powershell: … … 43 49 If you're not accustomed to Powershell you can just use ''mmc.exe'' and the certificate snap-ins to install the certificate. 44 50 45 == Querying the certificate store==51 === Querying the certificate store === 46 52 47 53 To list all certificates in ''Currentuser\My'' store using Powershell: … … 56 62 The ''dir'' command is just an alias for ''Get-!ChildItem'' 57 63 58 == Creating catalog files with inf2cat==64 === Creating catalog files with inf2cat === 59 65 60 66 To create a catalog file for a 32-bit driver: … … 73 79 '''NOTE:''' According to Microsoft Inf2Cat requires a full path to the driver directory. 74 80 75 == Signing files with signtool.exe==81 === Signing files with signtool.exe === 76 82 77 83 Sign a file using a (non-EV) certificate stored in a pfx file. Note that this process is not suitable for EV certificates, which are probably all stored in some sort of dongle and thus only visible through the Windows Certificate Store: … … 93 99 }}} 94 100 95 == Validating signatures==101 === Validating signatures === 96 102 97 103 Verifying the Authenticode signature of a file using Powershell: … … 124 130 * [https://technet.microsoft.com/en-us/library/hh849805.aspx Get-AuthenticodeSignature] 125 131 * [https://technet.microsoft.com/en-us/library/hh848625.aspx Import-PfxCertificate] 126
