{"id":4102,"date":"2016-03-01T20:00:18","date_gmt":"2016-03-01T19:00:18","guid":{"rendered":"http:\/\/www.samlogic.net\/blog\/?p=4102"},"modified":"2019-07-07T18:12:48","modified_gmt":"2019-07-07T18:12:48","slug":"visual-installer-now-supports-sha-2-and-dual-code-signing","status":"publish","type":"post","link":"https:\/\/www.samlogic.net\/blog\/2016\/03\/visual-installer-now-supports-sha-2-and-dual-code-signing\/","title":{"rendered":"Visual Installer now supports SHA-2 and dual code signing"},"content":{"rendered":"<p><img decoding=\"async\" class=\"alignright\" src=\"https:\/\/www.samlogic.net\/visual-installer\/pictures\/misc\/lock.jpg\" border=\"0\" alt=\"\">Since January 1, 2016, Windows 7 and newer Windows will no longer trust software that is signed with a <strong>SHA-1<\/strong> code signing certificate, if the software is downloaded from the Internet and the software is time-stamped with a value greater than January 1, 2016. This means that if you code sign a binary file (for example an EXE file) this year and uses SHA-1 as a hash algorithm, it will not be trusted in newer Windows. Instead you must use a <strong>SHA-2<\/strong> (<strong>SHA-256<\/strong>) code signing certificate; then the binary file will be trusted by Windows 7 and newer. You can read more about this in the following articles on Microsoft&#8217;s website:<\/p>\n<p><strong><span style=\"color: #ff0000;\">&gt;<\/span><\/strong> <a href=\"https:\/\/social.technet.microsoft.com\/wiki\/contents\/articles\/32288.windows-enforcement-of-authenticode-code-signing-and-timestamping.aspx\" target=\"_blank\" rel=\"noopener noreferrer\">Windows Enforcement of Authenticode Code Signing and Timestamping<\/a><br \/>\n<strong><span style=\"color: #ff0000;\">&gt;<\/span><\/strong> <a href=\"https:\/\/technet.microsoft.com\/library\/security\/3123479\" target=\"_blank\" rel=\"noopener noreferrer\">Deprecation of SHA-1 Hashing Algorithm for Microsoft Root Certificate Program<\/a><\/p>\n<p><strong>Updated Visual Installer<\/strong><br \/>\nWe have updated our installation tool <a href=\"https:\/\/www.samlogic.net\/visual-installer\/visual-installer.htm\" target=\"_blank\" rel=\"noopener noreferrer\">Visual Installer<\/a> to support SHA-2 (SHA-256) when it code signs a setup package. We have also updated Visual Installer to support dual signing, so you can code sign a setup package with both SHA-1 and SHA-2. This is very useful if you have software that should be able to run also in older Windows (for example in Windows XP). By code signing a setup package twice, first with SHA-1 and then with SHA-2, your code sign certificate will be useful in both older Windows and newer Windows.<\/p>\n<p><strong>How to change hash algorithm from SHA-1 to SHA-2<\/strong><br \/>\nIn Visual Installer you can change the hash algorithm from SHA-1 to SHA-2, for an existing project, by following the steps below:<\/p>\n<p><strong>1<\/strong>. Start Visual Installer<br \/>\n<strong>2<\/strong>. Open your project<br \/>\n<strong>3<\/strong>. Choose the <strong>Special &#8211; Setup options<\/strong> menu item<br \/>\n<strong>4<\/strong>. Open the <strong>Code Signing<\/strong> tab in the <strong>Setup options<\/strong> dialog box<br \/>\n<strong>5<\/strong>. Open the <strong>Option<\/strong> sub tab<br \/>\n<strong>6<\/strong>. Select the <strong>Use SHA-2<\/strong> option<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.samlogic.net\/visual-installer\/tips\/tips-pages\/code-sign-setup-package\/img\/vi-editor-setup-otions--code-signing-tab--6.png\" border=\"0\" alt=\"Code Signing - Use SHA-2\"><\/p>\n<p><strong>7<\/strong>. Close the dialog box<\/p>\n<p>If your minimum system requirements is Windows 7, you can use SHA-2 as a hash algorithm. But if you also want to support older Windows, follow the steps below:<\/p>\n<p><strong>How to dual sign a setup package (SHA-1 and SHA-2)<\/strong><br \/>\n<strong>1<\/strong>. Start Visual Installer<br \/>\n<strong>2<\/strong>. Open your project<br \/>\n<strong>3<\/strong>. Choose the <strong>Special &#8211; Setup options<\/strong> menu item<br \/>\n<strong>4<\/strong>. Open the <strong>Code Signing<\/strong> tab in the <strong>Setup options<\/strong> dialog box<br \/>\n<strong>5<\/strong>. Open the <strong>Option<\/strong> sub tab<br \/>\n<strong>6<\/strong>. Select the <strong>Use SHA-1 and SHA-2 (recommended)<\/strong> option<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.samlogic.net\/visual-installer\/tips\/tips-pages\/code-sign-setup-package\/img\/vi-editor-setup-otions--code-signing-tab--7.png\" border=\"0\" alt=\"Code Signing -Use SHA-1 and SHA-2\"><\/p>\n<p><strong>7<\/strong>. Close the dialog box<\/p>\n<p><strong>When you open your project file<\/strong><br \/>\nIf you have installed the latest version of <strong>Visual Installer 2015<\/strong> (version <strong>10.5.16<\/strong> or later) and opens a project file, you may see this message box when you open your project:<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/www.samlogic.net\/visual-installer\/tips\/tips-pages\/code-sign-setup-package\/img\/vi-editor-msgbox-information-update-signtool.png\" border=\"0\" alt=\"Update SignTool.exe\"><\/p>\n<p>It is recommended to answer yes, so the latest version of Microsoft&#8217;s code signing tool is used when a setup package is code signed. If you want to dual sign a setup package, you must have a quite new version of the code signing tool. You can read more in <a href=\"https:\/\/www.samlogic.net\/blog\/2016\/03\/where-can-i-find-the-latest-version-of-signtool-exe\/\">this blog post<\/a>.<\/p>\n<p><strong>Available in Visual Installer 2015 version 10.5.16 and later<\/strong><br \/>\nThe functionality described above is available in <strong>Visual Installer 2015<\/strong> version <strong>10.5.16<\/strong> and later; in both the Standard and Professional versions of Visual Installer. If you have an active 1 or 12 months <a href=\"https:\/\/www.samlogic.net\/fullversions-information\/download-latest-product-version-info.htm\" target=\"_blank\" rel=\"noopener noreferrer\">maintenance plan<\/a> for Visual Installer 2015, you can download this update for free from our download page.<\/p>\n<p><strong>See also<\/strong><br \/>\n<strong><span style=\"color: #ff0000;\">&gt;<\/span><\/strong> <a href=\"https:\/\/www.samlogic.net\/blog\/2016\/03\/what-is-sha-1-and-sha-2-and-whats-the-difference-between-them\/\">What is SHA-1 and SHA-2 and what\u2019s the difference between them?<\/a><br \/>\n<strong><span style=\"color: #ff0000;\">&gt;<\/span><\/strong> <a href=\"https:\/\/www.samlogic.net\/visual-installer\/tips\/tips-pages\/code-sign-setup-package\/code-sign-setup-package.htm\" target=\"_blank\" rel=\"noopener noreferrer\">How to code sign a setup package (Visual Installer tip)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Since January 1, 2016, Windows 7 and newer Windows will no longer trust software that is signed with a SHA-1 code signing certificate, if the software is downloaded from the Internet and the software is time-stamped with a value greater than January 1, 2016. This means that if you code sign a binary file (for &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/www.samlogic.net\/blog\/2016\/03\/visual-installer-now-supports-sha-2-and-dual-code-signing\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Visual Installer now supports SHA-2 and dual code signing&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[10,15],"tags":[],"_links":{"self":[{"href":"https:\/\/www.samlogic.net\/blog\/wp-json\/wp\/v2\/posts\/4102"}],"collection":[{"href":"https:\/\/www.samlogic.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.samlogic.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.samlogic.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.samlogic.net\/blog\/wp-json\/wp\/v2\/comments?post=4102"}],"version-history":[{"count":2,"href":"https:\/\/www.samlogic.net\/blog\/wp-json\/wp\/v2\/posts\/4102\/revisions"}],"predecessor-version":[{"id":6047,"href":"https:\/\/www.samlogic.net\/blog\/wp-json\/wp\/v2\/posts\/4102\/revisions\/6047"}],"wp:attachment":[{"href":"https:\/\/www.samlogic.net\/blog\/wp-json\/wp\/v2\/media?parent=4102"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.samlogic.net\/blog\/wp-json\/wp\/v2\/categories?post=4102"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.samlogic.net\/blog\/wp-json\/wp\/v2\/tags?post=4102"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}