Glossary
What are PAdES, CAdES and CMS signatures?
CMS is the container for a digital signature, CAdES builds on it for any file, and PAdES puts it in a PDF. See how they relate and which SignatureAPI uses.
A digital signature is a few kilobytes of data: the signature value, the signer’s certificate and some signed attributes. A signature format says how that data is packaged and where it goes. Three names come up most often.
CMS
CMS (Cryptographic Message Syntax, RFC 5652) is the container. It grew out of PKCS#7, so the two names are often used for the same thing. A CMS signature holds:
- The signed attributes: what was signed (a hash of the content), the content type, and often the signing certificate.
- The signature value over those attributes.
- The certificates needed to check it.
A detached CMS signature carries only the signature, not the content it signs. The content travels separately, which is how both formats below use it.
CAdES
CAdES (CMS Advanced Electronic Signatures, ETSI EN 319 122) is a profile of CMS for signing any file. It fixes which attributes must be present, such as a reference to the signing certificate, so that a signature can meet the eIDAS requirements for an advanced signature. A CAdES signature usually sits next to the file it signs, often as a .p7s file.
PAdES
PAdES (PDF Advanced Electronic Signatures, ETSI EN 319 142) puts a CAdES-style CMS signature inside a PDF. The PDF reserves space for the signature, and the signature covers every other byte of the file. PDF readers such as Adobe Acrobat find it and list it in their signature panel, so the recipient never handles a separate signature file.
Baseline levels
CAdES and PAdES both define baseline levels that add data for long-term checks:
| Level | Adds |
|---|---|
| B-B | The basic signature: signed attributes, signature value and certificate. |
| B-T | A trusted timestamp on the signature, proving when it existed. |
| B-LT | Validation data (certificate chain and revocation information), so the signature can be checked after the certificates expire. |
| B-LTA | Archive timestamps that protect the validation data itself over time. |
Formats in SignatureAPI
- Deliverables. SignatureAPI seals every deliverable with a signature inside the PDF, with a trusted timestamp. A PDF reader reports it as a valid signature. See Verify a deliverable.
- Qualified signatures. Each qualified signature is a PAdES signature. The signing worker supplies the basic signature, and SignatureAPI adds the signature timestamp (B-T) and the validation data (B-LT).
- Signing workers. A worker returns either a bare signature value (
raw) or a complete detached CMS signature (cms). Either way, SignatureAPI embeds it in the PDF.
The layers of a qualified signature, and where each one comes from:
Diagram as text
Parts
- Signature (PAdES B-B): The signature your worker returns from the sign call, over the digest SignatureAPI sent, with the certificate chain from credential (raw format) or sign (cms format).
- Signature timestamp (B-T): From SignatureAPI's timestamp authority. It replaces any timestamp in a provider's CMS, and every certificate must be valid at its time.
- Validation data (B-LT): Certificates, OCSP responses and CRLs in the PDF's Document Security Store. Your worker sends no revocation data.
Connections
- Signature (PAdES B-B) to Signature timestamp (B-T): timestamped
- Signature timestamp (B-T) to Validation data (B-LT): validation data appended
For the details a worker developer needs, see Signature formats.
Related
- Document hash: what a signature is computed over.
- Trusted timestamp: the B-T layer.
- Glossary: other terms.