Changes between Version 18 and Version 19 of BuildingTapWindows6

Timestamp:

02/03/17 13:58:27 (7 years ago)

Author:

Samuli Seppänen

Comment:

--

BuildingTapWindows6

@@ -30 +30 @@
 '''On build computer'''
 
-Run ''buildtap.py'' using the SHA1 certificate for signing. Make sure to include the correct cross-certificate and to timestamp the signature:
+Copy your kernel-mode SHA1 code-signing certificate and the intermediate cross-signing certificate to the tap-windows6 directory. 
+
+Run ''buildtap.py'' to build and to sign with SHA1
 
 {{{
-$ python buildtap.py -b <certificate-options>
+$ python buildtap.py -b --sign <certificate-options>
 }}}
 
@@ -46 +48 @@
 '''On code-signing computer'''
 
-Clone the [https://github.com/mattock/sign-tap6/ Sign-Tap6] repository. Copy ''tap6.tar.gz'' to the ''sign-tap6'' directory and extract it:
+Clone the [https://github.com/mattock/sign-tap6/ Sign-Tap6] repository. Ensure your SHA2 EV code-signing certificate is visible in the Windows certificate store, and copy the matching cross-certificate to the sign-tap6 directory.
+
+Copy ''tap6.tar.gz'' to the ''sign-tap6'' directory and extract it:
 
 {{{
@@ -59 +63 @@
 }}}
 
-Next append secondary signatures to ''tapinstall.exe'' and ''tap0901.cat'' files under ''tap6'' using [https://github.com/mattock/sign-tap6/ Sign-Tap6.ps1]. Ensure that you're using the correct cross-certificate and that you timestamp the signature.
+Next append secondary signatures with Sign-Tap6.ps1. For example:
+
+{{{
+$ Sign-Tap6.ps1 -SourceDir tap6 -Append
+}}}
 
 Now wrap the dual-signed files into a tarball (e.g. using Git Bash):