Changes between Version 38 and Version 39 of BuildingTapWindows6
- Timestamp:
- 04/06/19 07:08:49 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BuildingTapWindows6
v38 v39 105 105 }}} 106 106 107 Add a DDF file which is used to create the cabinet file. For example:108 109 {{{ 110 ; tap-windows6 .ddf107 Next you need to create three DDF files, one for each architecture (x86, x64, arm64), which are used to create the cabined files. Here's an example for amd64: 108 109 {{{ 110 ; tap-windows6-amd64.ddf 111 111 ; 112 112 .OPTION EXPLICIT ; Generate errors … … 121 121 .Set Compress=on 122 122 ;Specify file name for new cab file 123 .Set CabinetNameTemplate=tap-windows6 .cab123 .Set CabinetNameTemplate=tap-windows6-amd64.cab 124 124 ;Specify files to be included in cab file 125 .Set DestinationDir=i386126 C:\users\sign\opt\sign-tap6\tap6\i386\tap0901.sys127 C:\users\sign\opt\sign-tap6\tap6\i386\OemVista.inf128 125 .Set DestinationDir=amd64 129 126 C:\users\sign\opt\sign-tap6\tap6\amd64\tap0901.sys 130 127 C:\users\sign\opt\sign-tap6\tap6\amd64\OemVista.inf 131 .Set DestinationDir=arm64132 C:\users\sign\opt\sign-tap6\tap6\arm64\tap0901.sys133 C:\users\sign\opt\sign-tap6\tap6\arm64\OemVista.inf134 128 }}} 135 129 … … 137 131 138 132 {{{ 139 makecab.exe /f "C:\Users\sign\opt\sign-tap6\tap-windows6 .ddf"133 makecab.exe /f "C:\Users\sign\opt\sign-tap6\tap-windows6-amd64.ddf" 140 134 }}} 141 135 … … 143 137 144 138 {{{ 145 SignTool sign /ac "C:\Users\sign\opt\sign-tap6\digicert-high-assurance-ev.crt" /s MY /n "OpenVPN" /fd sha256 /tr http://timestamp.digicert.com /td sha256 /v "C:\Users\sign\opt\sign-tap6\disk1\tap-windows6.cab" 146 }}} 147 148 Now you have a signed cabined file. 149 150 Finally submit the signed cabined file to Windows Dev Center for attestation signing. 139 SignTool sign /ac "C:\Users\sign\opt\sign-tap6\digicert-high-assurance-ev.crt" /s MY /n "OpenVPN" /fd sha256 /tr http://timestamp.digicert.com /td sha256 /v "C:\Users\sign\opt\sign-tap6\disk1\tap-windows6-amd64.cab" 140 }}} 141 142 For other platforms just replace "amd64" with "i386" or "arm64". After this process you have three signed cabined files. 143 144 Now submit each one individually to Windows Dev Center for attestation signing. Make sure to check only the applicable platforms in the "Requested signatures" section. If all goes well, you can click "More" at the right of your submission below "Package and signing properties" and download a ZIP file with signed driver files. 145 146 Once you have the signed driver files you may want to wrap them into an installer. 151 147 152 148 For more generic instructions and more details please refer to the [https://docs.microsoft.com/en-us/windows-hardware/drivers/dashboard/attestation-signing-a-kernel-driver-for-public-release official MS documentation] on attestation signing.