I'm afraid currently this is not possible to do. Also, can you please give us more details about this? Why would you like to have the EXEs "touched" back to their original (pre-digital-signature-added) date and time ?
Hi Dan,
The reason is minor, but for example if the build is one that is tested and passes QA then the documented, QA-accepted build time and date would be nice to match the copy of those files that is shipped to the client. It's more of a question of "OK, we know exactly what was shipped to the client!!!" because the date/time and size would match some internally stored copy of those EXEs. If they don't match exactly then one always has the miniscule (but slightly greater than 0) probability that our tested base EXEs are not 100%-matched to what is shipped.
I suppose if we incorporate the dig-sig steps in what is QA tested then I can remove the dig-sig steps from AI, and then no "touch" scneario would be needed...? Is that right?
FOLLOW US
Get the latest news in Application Packaging