signtool

Publish Building using ClickOnce Stalls forever

别说谁变了你拦得住时间么 提交于 2019-12-11 07:37:36
问题 We use Click once technology to publish our application. Of late, when trying to do the same the application blocks for ever when the Sign Click once manifest is ticked. However, if this were to be uniticked or if the application were to published in safe mode with networking prompt , the publish build process doesnot hang. On the other hand if the application is run on normal mode with the sign manifest enabled the application always stops at the publish building process. Note: The

VB6 Digitally-Signed EXE appears as Unknown Publisher in Windows 8 SmartScreen

我与影子孤独终老i 提交于 2019-12-09 23:45:56
问题 I have compiled a VB6 app and I digitally sign it after compilation using a batch file containing this command: signtool sign /f apt.pfx /p MyPassword d:\upload\service_pack_UK_BETA.exe If I right-click the EXE I can see the digital signature in the file Properties. However if people download the file and try to run it in Windows 8 they get the message in SmartScreen that it's from an Unknown Publisher. I have read articles such as this one http://social.msdn.microsoft.com/Forums/windows/en

How to Sign an EXE with Additional Certificates using CryptoAPI and SignerSign

瘦欲@ 提交于 2019-12-09 21:45:10
问题 I'm trying to build a tool that will mass sign a bunch of files based on Kernel-Mode Code Signing requirements. I know that signtool can take an additional certificate for cross-signatures trust via the /ac argument, but have not been able to figure out how to do the same using SignerSign or SignerSignEx. I've even spied on signtool's API calls, and mirroring them does not seems to produce the same affect. Be aware, signtool or other command-line utilities cannot be used for this purpose due

MSBuild SignFile task returning MSB3481: The signing certificate could not be located

邮差的信 提交于 2019-12-09 12:59:53
问题 I recently got a new code signing certificate. I'm using MSBuild's SignFile task to sign an application manifest. For some reason the task is returning: MSB3481: The signing certificate could not be located. Ensure that it is in the current user's personal store. The certificate is definitely in my personal store, I can see it in certmgr.msc. And I believe that I'm logged in as the same user since I'm able to sign the manifest using a different certificate that is in the same personal store.

Why's My Root Certificate Not Trusted?

我怕爱的太早我们不能终老 提交于 2019-12-09 07:43:35
问题 I have issued myself a Code Signing certificate from a certificate server. I have also issued myself the root certificate from the same certificate server. The root certificate exists in both the Current User and Local Computer certificate stores within the Trusted Root Certification Authorities folder. I have successfully signed a DLL using the signtool.exe wizard: "C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\signtool.exe" signwizard <MyDLLName>.dll However, when I try to verify my DLL

Signing installer of my program generated by Inno Setup to make it of a trusted company? [duplicate]

岁酱吖の 提交于 2019-12-06 15:15:58
问题 This question already has answers here : Is it useless to sign my Windows application with a self signed certificate? (2 answers) Closed 5 months ago . I have a installer file created with Inno Setup of an application that I developed. So when I go to install the program, it shows me a window telling me that my application is not trusted. How can I sign my installer file to avoid that window when a user installs my program, or to make my installer a trusted installer? I have a .pfx file that

How do I use signtool in post build event for Visual Studio 2013 without hard coding path?

烈酒焚心 提交于 2019-12-05 20:52:50
I've created a post build event to do code signing of the application after a successful build with the following post build script. copy $(TargetPath) $(TargetDir)SignedApp.exe signtool sign /t http://timestamp.verisign.com/scripts/timestamp.dll /a $(TargetDir)SignedApp.exe I get the error 'signtool' is not recognized as an internal or external command. So it seems the path used for the build event doesn't point to the signtool utility. When I run the VS2013 x86 Native Tools Command Prompt I can run signtool as it includes a path which points to: C:\Program Files (x86)\Windows Kits\8.1\bin

PVK2PFX Error 0x80070490 - Cannot find certificates that match the key

倾然丶 夕夏残阳落幕 提交于 2019-12-05 12:57:28
We got our new certificate (*.cer) file from Thawte, and i went through our standard procedures to allow it for use with code signing. If i use our old (working) certificate: Convert certificate ( .cer) into Software Publishing Certificate ( .spc) >Cert2Spc.exe Avatar.cer Avatar.spc Succeeded Combine our private key file (*.pvk) with the SPC into a PFX: >pvk2pfx.exe -pvk Avatar.pvk -spc Avatar.spc -pfx Avatar.pfx -f prompts for private key file password, enter it, click OK And we're good to go; ready to use signtool . We now have our new certificate, and i follow the same procedure: Convert

Signing installer for windows app using electron builder

给你一囗甜甜゛ 提交于 2019-12-05 02:07:44
问题 I am using electron-builder for creating installer for my desktop app in windows by command build -w it cerates folder win-unpacked(for build) and win(for installer) here is my package.json { "name": "CoDesktopElectron", "version": "1.0.0", "description": "CoDesktopElectron", "homepage": "https://app.onepgr.com/", "author": "ankur", "private": true, scripts": { "postinstall": "install-app-deps", "start": "npm install && npm run compile && electron ./app", "compile": "rimraf app/out && tsc",

Signing installer of my program generated by Inno Setup to make it of a trusted company? [duplicate]

旧巷老猫 提交于 2019-12-04 20:48:35
This question already has an answer here: Is it useless to sign my Windows application with a self signed certificate? 2 answers I have a installer file created with Inno Setup of an application that I developed. So when I go to install the program, it shows me a window telling me that my application is not trusted. How can I sign my installer file to avoid that window when a user installs my program, or to make my installer a trusted installer? I have a .pfx file that I generated with OpenSSL and my SSL certificate. I tried signing it with the Inno Setup signing tool but without success. This