signtool

问题 We sign our executables on the build server. Suddenly the build server failed to build giving the error: SingTool Error: The sepcified timestamp server either could not be reached or returned an invalid response. After changing the timestamp server to http://sha256timestamp.ws.symantec.com/sha256/timestamp, singing did work again. Are there any issues with our old url? Why is it not available anymore? Could we have some (security) issues with the old signed files or the new url? I know this

问题 How to install SignTool.exe in Visual Studio 2015 for Windown 10? I tried to build my project but the program threw an error : Error An error occurred while signing: SignTool.exe not found. 回答1: You need to install the Windows 10 SDK. Visual Studio 2015 Update 1 contains it already, but it is not installed by default. You should go to Control Panel -> Programs and Features, find Microsoft Visual Studio 2015 and select "Change". Visual Studio 2015 setup will start. Select "Modify". In Visual

问题 How do you get the path to SignTool.exe when using Visual Studio 2012? In Visual Studio 2010, you could use <Exec Command=""$(FrameworkSDKDir)bin\signtool.exe" sign /p ... /> Where $(FrameworkSDKDir) is "c:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\" But in Visual Studio 2012, $(FrameworkSDKDir) is "C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\bin\" and SignTool is in "c:\Program Files (x86)\Windows Kits\8.0\bin\x64\" Is there a way of getting the path to this directory

问题 So, I've got a program I made in python 2.6, it ran fine as normal python, and ran fine when made into an exe via py2exe v0.6.9. I used signtool to sign it, having changed nothing else, and it stops working. When I run the signed exe, I receive an "ImportError: No module named os" from line 1 of my script. I did some digging and found this: http://osdir.com/ml/python.py2exe/2008-04/msg00031.html, which seems to be a very close description of my problem. I manually applied the patch linked to

问题 I'm trying to sign an ActiveX control with a code signing certificate issued by Thawte. I was able to successfully sign the control using signtool.exe. When I look at the file properties, it says "The certificate in the signature cannot be verified." When I view the certificate it says "Windows does not have enough information to verify the certificate." On the certification path tab, it says "The issuer of this certificate cannot be found." In internet explorer, the certificate is recognized

问题 OK - so this is really odd. I have a TFS build that signs a file and I'm getting the message above. If I look at the log from the build it says that it successfully signed and timestamped my file, (there's a .proj file that manually calls signtool) but below that in a different step (not sure where exactly) - I assume that its in the ClickOnce signing I get the error. I'm able to sign the file myself using Signtool using the same parameters as the build uses so I thought perhaps I needed to

问题 I'm trying to make an USB driver to be installable in Windows 8, this USB driver uses only WinUSB. According to this post Signed INF driver works on the computer where it was signed, not others and also this website Practical Windows Code and Driver Signing all I have to do is to generate an .inf file, to generate a .cat file and sign this .cat file, but I'm having trouble with the signing part, the other steps are ok. The sites I listed above makes clear that to sign a catalog file which the

问题 I am using signtool.exe to sign exe file. I am trying to embed my exe file with the .pfx certificate along with the signed hash of exe(generated signed hash using openssl). I am able to sign only with certificate. But I need to embed the signed hash in the exe as well. Probably signtool.exe sign /as could help. /as option does not expect any argument so not able to pass my hash there. Could someone please help me sign my exe with certificate and hash. Thanks, 回答1: The version of Signtool

问题 I am creating an Appx package using makeappx.exe and then try to sign it using SignTool.exe . The error I get from SignTool is: "Error: SignerSign() failed." (-2147024693/0x800700cb) The certificate I am using is created by me following instructions from here. In EventViewer there is no record about this failed operation! I do not understand what this error means and how to fix it!! Has anyone encountered this before, and found a solution? I can't use Visual Studio so I need to stick with

问题 As part of our build system, we use signtool.exe with a certificate to sign our binaries once they've been built. Occasionally (it's hard to tell when it will strike), the signing fails: error MSB3073: The command "C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\bin\signtool.exe" [...] exited with code 1. According to the MSDN, an exit code of 1 means that there was an error signing the file. I can verify that the file didn't get signed. I've also noticed that occasionally, the timestamp