THPDFSignatureVerifyStatus Type
Reports how verification of a loaded CMS signature turned out
Declaration
THPDFSignatureVerifyStatus= (
svNotVerified, // parsed only; VerifyLoadedSignature not run yet
svValid, // digest matches and signature verifies
svDigestMismatch, // document bytes changed after signing
svSignatureInvalid, // cryptographic signature check failed
svUnsupportedAlgorithm, // unknown key, curve, or digest algorithm
svMalformed, // CMS structure could not be parsed
svSourceUnavailable, // no source bytes available to hash
svCryptoProviderError, // native cryptographic provider failed
svInvalidByteRange, // /ByteRange is malformed, overlapping, or out of bounds
svDigestAlgorithmMismatch, // CMS digest algorithm identifiers are inconsistent
svSignaturePolicyMismatch // required or pinned signature policy did not match
);
Unit
HPDFSignVerify
Values
| Value | Meaning |
|---|---|
svNotVerified |
The signature was merely parsed; VerifyLoadedSignature has yet to run |
svValid |
The digest matches and the signature checks out |
svDigestMismatch |
The document bytes were altered after signing |
svSignatureInvalid |
The cryptographic signature check did not succeed |
svUnsupportedAlgorithm |
An unrecognised key, curve or digest algorithm was met |
svMalformed |
The CMS structure proved unparseable |
svSourceUnavailable |
There are no source bytes available to hash |
svCryptoProviderError |
The native cryptographic provider fell over |
svInvalidByteRange |
The /ByteRange entry is malformed, overlaps or runs out of bounds |
svDigestAlgorithmMismatch |
The CMS digest algorithm identifiers do not agree |
svSignaturePolicyMismatch |
The required or pinned signature policy failed to match |
Usage notes
svValidmeans the document bytes match what the embedded certificate's key signed; certificate chain and trust validation remain out of scope- The verify methods hand back this status per signature, and batch validation additionally reports an overall status