Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Using SignCheck to verify that a file is not signed
See original GitHub issueIs there a way to verify that a file isn’t signed using SignCheck?
Core-Setup produces a couple of template files, apphost.exe/comhost.dll, that must not be signed, and I’m concerned that slight changes to logic might cause signing to pick it up at some point. If that happens, I want it to break the Core-Setup official build. More info about the templates: https://github.com/dotnet/core-setup/pull/7549.
If that’s not possible (and I suppose it’s fairly niche), would it be possible to add this feature?
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
OK, from the tools perspective the simplest thing would be to have something similar to the exclusion file, and anything in that file, found to be signed would generate an error. This would give you the same flexibility to specify the parent files/container paths or use the hashed paths for the check.
I can probably look at it tomorrow
It’s not supported right now, but I can definitely see the need for this feature.
Are there copies of these files that must be signed as well, e.g. can the installer carry two copies in different folders, one that must be signed and one that shouldn’t be signed?