From ee9db7e262245200fa081181be9ad6721cc69001 Mon Sep 17 00:00:00 2001 From: Simon Rozman Date: Tue, 14 Mar 2017 09:44:31 +0100 Subject: [PATCH] Reverted to SHA1 Authenticode signatures for Windows XP compatibility --- README.md | 2 +- include/Release.props | 22 +--------------------- 2 files changed, 2 insertions(+), 22 deletions(-) diff --git a/README.md b/README.md index 5aee437..9ac6e21 100644 --- a/README.md +++ b/README.md @@ -23,7 +23,7 @@ In order to have the build process digitally sign output files, one should provi 1. A signing certificate installed in the current user's certificate store. 2. The following variables in the environment: - `ManifestCertificateThumbprint` - set the value to certificate's SHA1 thumbprint (hexadecimal, without spaces, i.e. `bc0d8da45f9eeefcbe4e334e1fc262804df88d7e`). - - `ManifestTimestampRFC3161Url` - set the value to URL used to perform RFC3161 timestamp signing (i.e. `http://sha1timestamp.ws.symantec.com/sha1/timestamp`). In order to perform timestamp signing successfully, the computer running the build should be online and able to access this URL. + - `ManifestTimestampUrl` - set the value to URL used to perform timestamp signature (i.e. `http://timestamp.verisign.com/scripts/timstamp.dll`). In order to perform timestamp signing successfully, the computer running the build should be online and able to access this URL. Please note that only Release builds are configured for timestamp signing. Debug configurations do not attempt to timestamp sign the resulting DLL and EXE files in order to speed up the building process and enable offline building. diff --git a/include/Release.props b/include/Release.props index c1872bd..5520a74 100644 --- a/include/Release.props +++ b/include/Release.props @@ -26,30 +26,10 @@ Full - - - - AnySuitable - - - - true - - - - Speed - - - - true - - - - true NDEBUG;%(PreprocessorDefinitions) MultiThreadedDLL @@ -67,7 +47,7 @@ Reverted to signtool.exe until we can drop Windows XP and Vista support. --> - + \ No newline at end of file