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.
SignFile returning code -2146762749
See original GitHub issueI’m coming to this from @onovotny’s https://github.com/onovotny/SignService which includes this library.
I’m seeingAuthenticodeKeyVaultSigner.SignFile return a code of -2146762749 which googling tells me may be coming from something called WinTrust or WinVerifyTrust. In my case I suspect this is because I am testing with a certificate that is self-signed.
Does anyone have any thoughts on this? Am I on the right track with this or is this likely something else? Should I expect this to work with a self-signed certificate?
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (4 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
@onovotny and @vcsjones thank you for your thoughts on this! Kevin you are exactly right. I was testing with text file that i just added an .exe too… As soon as changed it to a real exe file everything worked.
The tool should work with a self-signed certificate. I use that regularly for my testing (though I believe the dates must be valid).
@vcsjones would know more.