Documentation/Nightly/Developers/Windows Code Signing - Revision history

JChris.FillionR: /* Sign using SHA-2 (use to sign Slicer installer) */

2019-01-16T15:55:50Z

Sign using SHA-2 (use to sign Slicer installer)

2019-01-16T15:55:40Z

Sign using SHA-2 (use to sign Slicer installer)

2019-01-16T15:54:59Z

Sign using SHA-2 (use to sign Slicer installer)

2019-01-16T15:41:31Z

Sign using SHA-2

2017-12-27T08:03:33Z

Sign using SHA-2

2017-10-19T01:18:56Z

Sign using SHA-2

2017-10-18T23:16:46Z

Prerequisites

2016-12-05T19:12:08Z

Improve signing command line example

2016-12-05T19:09:32Z

2016-12-05T18:17:50Z

Verify the signature

@@ Line 25: / Line 25: @@
 ===Examples===
-====Sign using SHA-2 (use to sign Slicer installer)====
+====Sign using SHA-2 (used to sign Slicer installer)====
 This is the recommended method, and was used to sign the Slicer installers starting with version 4.6.

@@ Line 26: / Line 26: @@
 ====Sign using SHA-2 (use to sign Slicer installer)====
-This is the recommended method, and was used to sign the Slicer 4.6 installers.
+This is the recommended method, and was used to sign the Slicer installers starting with version 4.6.
 ) Open a <i>Developer Command Prompt</i> (e.g VS2017 x64 Native Tools Command Prompt)

@@ Line 28: / Line 28: @@
 This is the recommended method, and was used to sign the Slicer 4.6 installers.
-) Open a <i>Developer Command Prompt</i> (e.g VS2015 x64 Native Tools Command Prompt)
+) Open a <i>Developer Command Prompt</i> (e.g VS2017 x64 Native Tools Command Prompt)
 ) Download the DigiCert signing certificate (<code>codecert.pfx</code>) and get associated <code>&lt;password&gt;</code> needed in the command below.

@@ Line 25: / Line 25: @@
 ===Examples===
-====Sign using SHA-2====
+====Sign using SHA-2 (use to sign Slicer installer)====
 This is the recommended method, and was used to sign the Slicer 4.6 installers.

@@ Line 28: / Line 28: @@
 This is the recommended method, and was used to sign the Slicer 4.6 installers.
-) Open a <i>Developer Command Prompt</i>
+) Open a <i>Developer Command Prompt</i> (e.g VS2015 x64 Native Tools Command Prompt)
-) Sign using a DigiCert code signing certificate, following their [https://www.digicert.com/code-signing/signcode-signtool-command-line.htm examples]:
+) Download the DigiCert signing certificate (<code>codecert.pfx</code>) and get associated <code>&lt;password&gt;</code> needed in the command below.
 <pre>
-signtool.exe sign /f "C:\path\to\cert.pfx" /p <password> /fd sha256 /tr http://timestamp.digicert.com /td sha256 /v \path\to\your\installer.exe
+signtool.exe sign /f "C:\Users\dashboard\Downloads\codecert.pfx" /p <password> /fd sha256 /tr http://timestamp.digicert.com /td sha256 /v "C:\Users\dashboard\Downloads\installer.exe"
 </pre>
 * <tt>/f</tt> specifies the path to the code signing certificate

← Older revision		Revision as of 23:16, 18 October 2017
Line 6:		Line 6:

	* Install [https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk Windows 10 SDK] to get latest [https://msdn.microsoft.com/en-us/library/8s9b9yaz(v=vs.110).aspx SignTool.exe].		* Install [https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk Windows 10 SDK] to get latest [https://msdn.microsoft.com/en-us/library/8s9b9yaz(v=vs.110).aspx SignTool.exe].
		+
		+	[[File:Windows 10 SDK-Installing-for-app-signing.png\|500px]]

	==Acquire and install a code signing certificate==		==Acquire and install a code signing certificate==

@@ Line 19: / Line 19: @@
 SignTool.exe digitally signs files, verifies signatures in files, and time-stamps files. See [https://msdn.microsoft.com/en-us/library/8s9b9yaz(v=vs.110).aspx SignTool.exe documentation].
-At a minimum, the final installer .exe should be signed.
+The final installer .exe should be signed.
 ===Examples===
@@ Line 74: / Line 65: @@
 Finally, see discussion on the CMake mailing list: http://cmake.3232098.n2.nabble.com/How-to-codesign-msi-from-WIX-CPack-td7594228.html.
 ==Additional references==

@@ Line 59: / Line 59: @@
 </pre>
 * <tt>/pa</tt> specifies that the Default Authenticode Verification Policy should be used instead of the Windows Driver Verification Policy
 ===Notes===