Forum Discussion
vex
13 years agoContributor
Helen,
This sorta helps, but that is missing one key piece of information. While it will tell you the valid from and valid too dates, it doesn't seem to pull the actual timestamp of the certification. If I'm wrong, please correct me. Specifically, what I'm talking about is if you go to the file properties of a file, click "Digital Signatures" tab, and you'll see a timestamp there. That value is what I need to check for.
This can be done in powershell with the code in the original post, but I need to incorporate that into TestComplete.
The goal I'm trying to test for here is to check if a file is signed, and then to make sure the signing timestamp is != NULL. Also, using Capicom is unfortunately out of the question - I did see a lot of detail around that but that is very depreciated by Microsoft and our company policies will not let us build up automation relying on that component.
This sorta helps, but that is missing one key piece of information. While it will tell you the valid from and valid too dates, it doesn't seem to pull the actual timestamp of the certification. If I'm wrong, please correct me. Specifically, what I'm talking about is if you go to the file properties of a file, click "Digital Signatures" tab, and you'll see a timestamp there. That value is what I need to check for.
This can be done in powershell with the code in the original post, but I need to incorporate that into TestComplete.
The goal I'm trying to test for here is to check if a file is signed, and then to make sure the signing timestamp is != NULL. Also, using Capicom is unfortunately out of the question - I did see a lot of detail around that but that is very depreciated by Microsoft and our company policies will not let us build up automation relying on that component.
Related Content
- 7 years ago
- 7 years ago
Recent Discussions
- 3 days ago