askolits
asked on
Files loses it Code Signing Certificate when executed from another program
I have a small VB6 exe file that I have signed using a code signing certificate from GoDaddy.
I signed the file using Micrsofts SignTool.
I put the file on a Windows PC and execute it. No problem. Certificate is valid.
I can run it multiple times, and still valid.
I then I have another program (Access DB) that calls this file using a shell command.
Once it calls that file, it immediately makes the file's certificate invalid: "The Digital Signature Is Invalid"
This VB6 file has never been a problem for years. I recently had to make a small change to the file. Just one line of code.
BUt the VB6 program loses it's certificate even before it's executed.
I'm stumped.
Note: The VB6 file performs on FTP file download and works fine.
I signed the file using Micrsofts SignTool.
I put the file on a Windows PC and execute it. No problem. Certificate is valid.
I can run it multiple times, and still valid.
I then I have another program (Access DB) that calls this file using a shell command.
Once it calls that file, it immediately makes the file's certificate invalid: "The Digital Signature Is Invalid"
This VB6 file has never been a problem for years. I recently had to make a small change to the file. Just one line of code.
BUt the VB6 program loses it's certificate even before it's executed.
I'm stumped.
Note: The VB6 file performs on FTP file download and works fine.
ASKER
I've tried many methods of signing and resigning. You can sign within the VB6 development program the code as well as signing the created exe file itself.
Remember, it works fine on it's own. Only when I call it. Then after it gets called that one time from Access, I loses is certification.
I've never heard of Access caching files. I can look into it. And even if it did, why would the exe file lose it's cert completely when I try to execute it outside Access?
Remember, it works fine on it's own. Only when I call it. Then after it gets called that one time from Access, I loses is certification.
I've never heard of Access caching files. I can look into it. And even if it did, why would the exe file lose it's cert completely when I try to execute it outside Access?
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Also make sure the file isn't cached somehow in your Access application.