Closed mikkeljohnsen closed 2 years ago
Do you expect these 50+ DLL files to have an identical hash value? Otherwise, each hash value will produce a different signature, which in turn results a separate invocation of your internal certificate functions and a separate request to the timestamping server.
Yes, it takes time. On the other hand, how often you make a change in your code that affects 50+ different libraries? I guess you need to optimize your script to only sign the newly modified files.
I don't know the technical stuff, but I would assume I could sign 50+ DLL faster, than having to invoke osslsigncode on all files separately. But mayby that can't be done.
When we release a new version of our software, we compile it all again. Keeping track of changed DLL would be to error prone. It takes 4 min to compile but 10 min to sign.
I don't know the technical stuff, but I would assume
So I spent my valuable time explaining the technical stuff you you. Free of charge.
Is there a way to sign multiple files (DLL's) at the same time ?
I takes a long time to sign 50+ dll files, since, I assume, the timestamp server needs to be called.
Could there be a glob option for just pointing af all DLL's in one command, so the timestamp server is called only once, and I assume, other internal certificate functions could be performed only once.
That would mean the "-out" parameter should be invalid and the signed file, should just override the unsigned file.