Assertion: certificate's signature | /r/HasProperty | applied
Facets:
Source sentences:
text: There are two main reasons for including a trusted timestamp when you digitally sign a document – ensuring Long-Term Validation (LTV) of the signature and adding non-repudiation or confidence around when the signature was actually applied.
text: Part of the digital signature verification process involves a content integrity check, so while a timestamp also offers that benefit (knowing the document hasn’t been changed since the signature was applied), it’s not a major driver as it is with electronic signatures.
text: Adobe 9+ embeds revocation information (CRL or OCSP) at the time of signing, which achieves the same goal of verifying validity of the certificate when the signature is applied, so a timestamp is not needed for LTV.
text: This means they are not subject to tampering like a local system clock is, so you know with certainty when a signature was applied.
text: With a timestamp (and LTV), the signature will still be trusted since the signing certificate was valid when the signature was applied.
text: – since the individual is the only one with access to the private key used to apply the signature, he/she cannot later claim that it wasn’t him/her who applied the signature Integrity - when the signature is verified, it checks that the contents of the document or message match what was in there when the signature was applied.