PDF Digital Signatures vs Password Protection — Key Differences

What a digital signature actually does

A digital signature in a PDF, through a signature field or a DocMDP signature, cryptographically binds the signer's identity to the document content. It is created with the signer's private key, typically stored on a USB token, smart card or PKCS#12 file. The signature covers the document's byte range, so any modification after signing invalidates it.

Digital signatures DO NOT encrypt the document. A signed PDF is fully readable by anyone. The signature is embedded as a signature dictionary (/Sig) and references a field in the AcroForm. The signed content is hashed — SHA-256 or SHA-384 for modern signatures, SHA-1 for legacy — and the hash is encrypted with the signer's private key.

Verification needs the signer's public key certificate, included in the signature or fetched from a trust anchor. The verifier decrypts the signature hash with the public key, hashes the document independently, and compares. If the hashes match and the certificate chain is trusted, the signature is valid.

What password protection actually does

PDF password protection (the Standard Security Handler) encrypts the document content with a symmetric cipher: AES-256 for modern PDFs, AES-128 or RC4 for legacy versions. The password is transformed into a symmetric key through a key-derivation function.

When a PDF is password-protected, the content streams, other streams and strings, and the metadata stream are all encrypted. The file cannot be rendered or read without the correct password. The encrypt dictionary in the trailer stores the parameters but not the password.

Password protection also supports the owner/user password distinction. The user password opens the document; the owner password additionally allows changing permissions such as printing and editing. In PDF 2.0 (revision 6) the file encryption key is randomly generated and wrapped separately under the user (open) password and the owner (permissions) password. RC4 and the older derivation are deprecated, but both password roles remain.

How they interact when both are applied

A PDF can be both signed and encrypted. Encryption is applied first, or in the same save as the signature, so the signature covers the already-encrypted file bytes — applying password security after signing rewrites the covered bytes and invalidates the signature. The signature value itself (/Contents) is stored unencrypted so it stays readable, but the rest of the signature dictionary and the whole file are encrypted, and a validator hashes the raw file bytes rather than decrypted content.

The workflow is to apply encryption and the signature together, as Acrobat does. The signature then covers the stored bytes of the encrypted file. When a recipient opens the encrypted and signed document they must first enter the password, or use their private key for CMS encryption, so the content can be decrypted for rendering — but validation still runs against the file's byte range.

Practical implication: if you forget the password on a signed-and-encrypted PDF, recovery is needed only for the encryption layer. The signature does not lock the document; it only proves authenticity after decryption. Recovery works exactly as for an unsigned encrypted PDF (Hashcat mode 10700 for AES-256).

Signature types and their effects on modification

Certificate signatures (a simple signature field, /Sig): the document is signed by a user's certificate. The signature can cover specific byte ranges or the whole document. Multiple signatures can exist. Modifying a signed document breaks the original signature, but new signatures can be added.

DocMDP signatures (Document Modification Detection and Prevention): a special signature that restricts which modifications are permitted without breaking it. Permitted actions are defined in the signature's reference dictionary, for example filling forms, adding comments or signing. Changes outside those actions invalidate the signature.

UR signatures (Usage Rights): embedded by Adobe-based writers to enable extra features (saving, filling forms, adding comments) in Adobe Reader. They are technically signatures but relate to software licensing rather than document security.

Password protection is unaffected by signature type. The password gate operates independently of any signature restriction.

Recovery scenarios for signed and/or encrypted PDFs

Scenario 1: signed but not password-protected — fully readable, no recovery needed. The signature can be removed (Acrobat > Certificates > Remove Signature) or verified.

Scenario 2: password-protected and signed — recovery means password cracking only. The signature neither adds nor removes recovery difficulty. Use Hashcat modes 10400 to 10700 as appropriate.

Scenario 3: public-key encrypted (no password) and signed — the file key is encrypted to the recipient's public key, so decryption requires that recipient's private key. If the private key is lost and not escrowed, the document is unrecoverable regardless of the signature.

Scenario 4: a signature that prevents editing — this is DocMDP protection, not encryption. The content is readable. The restrictions can be removed by re-saving without the signature, or by editing the document catalog to remove the /Perms/DocMDP reference where permitted.

Signature-based permission restrictions

Some PDFs use an approval signature to restrict further modification: when a document is signed at a DocMDP level that permits only form filling and signing, any other change breaks the signature. This is NOT password encryption — the content stays fully readable.

Converting a signed-and-restricted PDF to one without modifications, for example by re-saving without the signature, removes the restriction but loses signature validation. For a user who only needs the content that is acceptable; for one who needs the signed original, the restriction must be respected.

If you have a signed PDF that blocks editing and want to edit it anyway: remove the signature in Acrobat Pro, re-save as a new PDF without it, then edit. The content is unaffected — only signature verification is lost.

Legal and compliance contexts

Frameworks such as the US ESIGN Act and the EU eIDAS Regulation give electronic signatures legal effect; only a qualified electronic signature under eIDAS is treated as equivalent to a handwritten one. Removing a digital signature from a legally executed document may affect its standing — even though the content is the same, the signature binding is lost.

Password-protected PDFs without signatures have no authentication: anyone with the password can open them. Signed PDFs without passwords have authentication but no access control. Together they give the strongest protection: only authorised people can read the content, and the signature proves who signed it.

In court proceedings, admissibility turns on the jurisdiction's own authentication and evidence rules rather than on who authorised the recovery, so treat it as a question for the receiving body. The signature itself remains valid after password recovery — recovery only obtains the password and rewrites nothing.