authenticode

Windows 10 ignores Authenticode on my setups files

房东的猫 提交于 2019-12-05 00:59:14
问题 Being on the "Fast Ring" of Windows 10, I got a strange behaviour on my own setup executables: I'm SHA-1 signing them with Authenticode since years the same way and never had any problems. Recently Windows 10 does not recognize my (valid) signatures. When downloading a setup.exe from my website and executing it, the Windows SmartScreen message box appears and tells me: ... Publisher: unknown ... When viewing the properties of the just downloaded setup executable, it shows the signature, and

Detect a digital signature without WinVerifyTrust

一世执手 提交于 2019-12-04 13:04:37
I have a large number of EXE files and need to figure out which ones have digital signatures. Does anyone know if there is a way to check without access to WinVerifyTrust (they're all on a Unix server). I can't seem to find any information on where the digital signature actually is inside the EXE. If I could find out where it is I might be able to open the file and fseek to a location to test. I don't need to do "real" verification on the certificate, I just want to see if a digital signature is present (or, more importantly, NOT present) without having to use WinVerifyTrust. As mentioned

Amended code to retrieve dual signature information from PE executable in Windows?

删除回忆录丶 提交于 2019-12-04 11:11:37
I've been struggling for awhile to amend this code sample from Microsoft that shows (somewhat outdated) way how to retrieve a code signature information from an executable file. It works but it doesn't retrieve information if a binary file is dual-signed. So I did some research and tried to rewrite it to make it recognize dual-signatures that are present in many modern executables in Windows. Unfortunately there are very few (nebulous) suggestion available ( 1 ), ( 2 ), such as those to use UnauthenticatedAttributes and szOID_NESTED_SIGNATURE (whatever that means) but only to retrieve a time

How do I read the digital signature information from a signed .Net assembly?

丶灬走出姿态 提交于 2019-12-04 02:46:12
I am writing an assembly information application to be used in our software build process and am trying to read the digital signature information from a signed .Net assembly. I want to do in my C# code what Windows Explorer can do by right-clicking a signed assembly and selecting the "Digital Signatures" tab and then clicking the Details button. e.g. Has anyone got an idea how to do this programmatically in C#? I am currently using the Mono Cecil library to get the rest of the information from the assembly. Your help will be most appreciated. The Mono project provides source code for both

Managed Windows Service starts up slowly after digital signing

南笙酒味 提交于 2019-12-03 20:04:57
问题 We recently tried out digitally signing our .NET binaries. We have a Windows Service which typically starts up within 10 seconds. However after we started digitally signing it, the time increased to around 20-30 seconds. Googling led to me this: http://support.microsoft.com/kb/936707 which basically says that I have to set generatePublisherEvidence to false. But the description of generatePublisherEvidence on MSDN points to the fact that this is not applicable for .NET 4. Still I tried out

Signed INF driver works on the computer where it was signed, not others

巧了我就是萌 提交于 2019-12-03 18:26:36
问题 My company purchased a Driver Signing Certificate from Go Daddy. I used it to sign a simple INF file that is a driver for some of our USB devices that use Microsoft's usbser.sys. Everything seems to work on the Windows 7 64-bit computer where I signed it: if I right-click on the INF file and select "Install" then the second warning I see is this good warning that shows the correct Publisher name: However, if I go to a different computer (Windows Vista 64-bit), right click on the INF file, and

How do I securely configure a CI server to digitally sign binaries?

做~自己de王妃 提交于 2019-12-03 07:12:02
问题 There are many sites that explain how to run signtool.exe on a .pfx certificate file, which boil down to: signtool.exe sign /f mycert.pfx /p mypassword /t http://timestamp.server.com \ /d "My description" file1.exe file2.exe I have a continuous integration CI process setup (using TeamCity) which like most CI processes, does everything: checks out source, compiles, signs all .exes, packages into an installer, and signs the installer .exe. There are currently 3 build agents, running identical

Code signing (Microsoft Authenticode) [closed]

☆樱花仙子☆ 提交于 2019-12-03 01:12:32
问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 6 years ago . I have a program which is used by a large number of people who are not always super computer savvy. I want to make sure that rather than having my executable say it is from an unknown author that it says it was signed by me. As far as I know this can be done with Microsoft Authenticode. I understand I need a

Reading multiple signatures from executable file

允我心安 提交于 2019-12-02 23:06:35
I am trying to write code that reads signatures (certificates) from DLLs or and EXEs. Most DLLs or EXEs have only one signature, and my code reads all certificates associated with this signature correctly. More specifically it reads signing cert, it's issuer (not root), countersigning cert (with timestamp) and its issuer (not root). I have 2 sample programs in C++ and C#, they both return the same certs. This is C# code, C++ is 100 times longer :) static void Main(string[] args) { X509Certificate2Collection collection = new X509Certificate2Collection(); collection.Import(args[0]); } But there

How do I securely configure a CI server to digitally sign binaries?

邮差的信 提交于 2019-12-02 20:44:27
There are many sites that explain how to run signtool.exe on a .pfx certificate file, which boil down to: signtool.exe sign /f mycert.pfx /p mypassword /t http://timestamp.server.com \ /d "My description" file1.exe file2.exe I have a continuous integration CI process setup (using TeamCity) which like most CI processes, does everything: checks out source, compiles, signs all .exes, packages into an installer, and signs the installer .exe. There are currently 3 build agents, running identical VMs, and any of them can run this process. Insecure implementation To accomplish this today, I do a