Re:Over half the firmwares uploaded to TCSL Armor have inval...
by hyperman1 on Monday September 17, 2018 @03:19AM
(#18003830)
I start to see how this works. There is a third party, but they intervene at signing time and not at validation time.
In detail: You create a hash of your executable and send it to the third party, the TSS. They sign the hash, and never even need to see the actual executable. As long as the end user trusts the third party's cert, the TSS can guarantee the executable existed in its current shape on the date you claim it existed. A kind of notary service.
For who wants to know more: Here is a Java article detailling how this works for Java, and what happens if the TSS cert itself expires
In detail: You create a hash of your executable and send it to the third party, the TSS. They sign the hash, and never even need to see the actual executable. As long as the end user trusts the third party's cert, the TSS can guarantee the executable existed in its current shape on the date you claim it existed. A kind of notary service.
For who wants to know more: Here is a Java article detailling how this works for Java, and what happens if the TSS cert itself expires
https://blogs.oracle.com/java-platform-group/signed-code-nee...
And wikipedia is interesting too:
https://en.wikipedia.org/wiki/Trusted_timestamping