You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/trusted-signing/faq.yml
-7Lines changed: 0 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -95,13 +95,6 @@ sections:
95
95
- question: How do we get the Authenticode certificate?
96
96
answer: |
97
97
The Authenticode certificate that's used for signing with the profile is never given to you. All certificates are securely stored within the service and are accessible only at the time of signing. The public certificate is always included in any binary that the service signs.
98
-
- question: What are the common steps I should complete if I get a SignTool error (for example, if an unexpected internal error occurs)?
99
-
answer: |
100
-
1. Check that the dlib and DLL files are in the correct path.
101
-
1. Check that the version of SignTool that's installed and the dlib are both 64-bit.
102
-
1. Download and install [C++ Redistributables](https://docs.microsoft.com/cpp/windows/latest-supported-vc-redist?view=msvc-170).
103
-
1. Search for the specific issue on Bing or review the [SignTool overview](https://docs.microsoft.com/windows/win32/seccrypto/signtool).
104
-
1. We recommend that you use [a specific version of SignTool](https://developer.microsoft.com/windows/downloads/windows-sdk/) instead of getting it directly from NuGet. In an earlier article, we tested the SignTool version and confirmed that it works with our dlib (version 10.0.22621 currently is recommended).
105
98
- question: How do I check whether the time stamp service is healthy?
106
99
answer: |
107
100
Run the following command: `curl http://timestamp.acs.microsoft.com`. If status code 200 is returned, the time stamp service is healthy and running.
0 commit comments