THPDFCMSDigestConsistencyIssue Type
Pinpoints which CMS digest consistency check failed while verifying a signature
Declaration
THPDFCMSDigestConsistencyIssue= (
dciNone,
dciSignerDigestNotDeclared,
dciSignatureDigestMismatch,
dciAlgorithmProtectionDigestMismatch,
dciAlgorithmProtectionSignatureMismatch
);Unit
HPDFSignVerify
Values
| Value | Purpose |
|---|---|
dciNone | Every digest consistency check passed |
dciSignerDigestNotDeclared | The signer's signed attributes do not declare the mandatory message-digest attribute |
dciSignatureDigestMismatch | The computed digest of the signed content does not match the declared message digest or the signature value |
dciAlgorithmProtectionDigestMismatch | The digest does not match the value protected by the algorithm-protection attribute |
dciAlgorithmProtectionSignatureMismatch | The signature algorithm does not match the algorithm pinned by the algorithm-protection attribute |
Usage notes
- A value other than
dciNoneaccompanies thesvDigestAlgorithmMismatchsignature status so callers can tell which identifier disagreed - The checks run in a fixed order and the first failing issue wins, so fix
dciSignerDigestNotDeclaredbefore reading later mismatches - The same analysis also runs inside RFC 3161 timestamp tokens, where the result surfaces on
THPDFTimestampInfo.DigestConsistencyIssue