When you "Password Protect" a PDF, the software generates an Encryption Dictionary. This dictionary takes your typed password, hashes it, and stores the resulting string under the /O (Owner) or /U (User) keys. It then calculates a master document key using AES or RC4, and scrambles every single piece of text, image stream, and metadata object in the file except the trailer and the Encryption Dictionary itself. When someone tries to open the file, the viewer reads the Encryption Dictionary, prompts them for a password, and attempts to reverse the mathematical process to decrypt the pages.
Security Handlers & Crypt Filters
The dictating architecture behind PDF encryption relies on two primary layers:
- Security Handlers (/Filter) — Determines *how* the document is authorized.
/Standard: Uses basic typed strings (User/Owner passwords)./PubSec: Uses Public Key Cryptography (Certificates).- Custom: Used by enterprise DRM servers (like Adobe LiveCycle or Microsoft Purview) where the PDF phones home to a server to ask permission to open.
- Crypt Filters (/CF) — In modern PDFs (Version 1.5+), you can define multiple cryptographic filters. For example, you can tell the PDF: "Encrypt the attachments with AES-256 (Filter A), but leave the main text pages unencrypted so search engines can read them (Filter B)." The
/StmFkey applies to Stream objects, and the/StrFkey applies to String objects.
Vulnerability of DRM: The /P permission value (which blocks printing or copying) is enforced by the "Honor System". If you provide a viewer the User Password, it physically decrypts the file. A compliant viewer reads /P and disables the print button. A rogue viewer ignores /P and prints the fully decrypted file anyway.
Historical Encryption Revisions
| Revision Code (/R) | Algorithm & Length (/V) | Security Status |
|---|---|---|
/R 2 | 40-bit RC4 (V=1) | Broken. Extremely weak due to 1990s US export regulations. Instantly brute-forced. |
/R 3 | 128-bit RC4 (V=2) | Obsolete. Stronger, but RC4 has known catastrophic cryptographic biases. |
/R 4 | 128-bit AES (V=4) | Secure. Introduced in PDF 1.6. The first modern implementation of secure block-cipher encryption. |
/R 5 | 256-bit AES (V=5) | Secure. Introduced in PDF 1.7. Requires Acrobat X or later to open. |
/R 6 | 256-bit AES (V=5) | Highly Secure. Introduced in PDF 2.0. Replaces weak SHA2/MD5 password hashes with PBKDF2 iterations to prevent brute-forcing. |
Real-World Scenarios
The HIPAA Patient Record
A clinic must email blood test results to a patient. Sending unencrypted PDFs risks intercept. The database software automatically generates the PDF and attaches an Encryption Dictionary. It sets the /Filter to /Standard, uses /R 6 (AES-256), and sets the User Password (/U) hash based on a combination of the patient's birth date and phone number. If intercepted on the network router, the attacker only sees mathematically scrambled ciphertext. The patient types their birthday + phone into Acrobat at home and the AES key decrypts the file.
The Copy-Protected EBook
An indie author sells their novel as a PDF download. They don't want readers pasting the text directly to pirate sites. They configure the Encryption Dictionary for "Permissions Only". They leave the User Password blank, but set a heavy 32-character Owner Password. They manipulate the Permission integer /P to turn off Bit 5 (Copying Text) and Bit 10 (Extracting Graphics). The buyer downloads the PDF, opens it without typing a password, and can read perfectly using Adobe Acrobat. But when they highlight text and press Ctrl+C, the OS dings, and the viewer refuses the action.
Unencrypted Metadata on Encrypted Files
A security firm publishes heavily encrypted technical teardowns on their website, meant only for logged-in subscribers holding the password. However, they still want Google to crawl the Title, Author, and Subject for SEO ranking. They set the Encryption Dictionary key /EncryptMetadata false. Now, the /Contents text stream is locked tight behind AES-256, but the XMP Metadata packet is left as plain, unencrypted XML text. Googlebot indexes the exact topic of the document flawlessly, even though it can never read the text inside.
Why the Encryption Architecture is Essential
Federal Standard Access
PDF adoption of AES-128 and AES-256 ensures compliance with FIPS and government/military standards for the secure communication of classified data.
Dual Password Hierarchy
The separation of User and Owner passwords allows a single document to be distributed safely—employees can open and read (User), but only the administrator can alter or redact (Owner).
Granular Workflow Control
The /P permissions integers allow highly specific edge-cases: e.g., "Allow filling in form fields and signing, but absolutely forbid altering the text or inserting new pages."
Selective Area Encryption
CryptFilters allow advanced designs: You can keep the text of a contract unencrypted, while ensuring the embedded XML billing data and image attachments are locked requiring a password.
Enterprise Server DRM
Instead of hardcoding a password in the file, custom Security Handlers can ping an enterprise database. If an employee is fired, their access is revoked on the server, and their local copy of the PDF becomes instantly unopenable.
Certificate Driven Identity
Using Public Key Security Handlers ensures that physical hardware tokens or biometric data can be integrated into the decryption sequence rather than relying on weak human memory passwords.
The Encryption Dictionary Structure
% This object is referenced by the /Encrypt key in the document trailer 15 0 obj << /Filter /Standard % Use password-based security /V 4 % V=4 denotes AES or RC4 128-bit /Length 128 % The encryption key length in bits /R 4 % Revision 4 algorithm (AES) % The calculated hash of the Owner password. Used for verification. /O <3A5B89...32 byte hex sequence...C421> % The calculated hash of the User password. /U <F6C201...32 byte hex sequence...D9BE> % 32-bit integer defining permissions. % -3904 specifies: No Printing, No Copying, No Editing. /P -3904 % Boolean: Should the XMP Document Info metadata be encrypted? /EncryptMetadata false % Crypt Filters (Defines the actual AES mapping) /CF << /StdCF << /Type /CryptFilter /CFM /AESV2 % Cryptographic Filter Method (AES Version 2) /Length 16 % 16 bytes = 128 bits /AuthEvent /DocOpen >> >> /StmF /StdCF % Apply StdCF to all Streams (Images/Pages) /StrF /StdCF % Apply StdCF to all Strings (Text outside streams) >> endobj
Common Encryption Mistakes
- Assuming DRM Permissions equal Security. Setting "Do not allow printing" without setting a User Open password encrypts the file mathematically using a blank string. The file is vulnerable. Any tech-savvy user can run the file through a free "PDF Password Remover" script which decrypts it using the blank string, ignores the
/Pflags, and saves a brand new, fully unprotected copy of your document. - Using ancient 40-bit RC4 for "compatibility". Choosing an older encryption standard so "people using ancient Mac OS preview from 2004 can open it." 40-bit encryption is so mathematically flawed it can be cracked by a modern iPhone in less than 300 milliseconds. Always use AES.
- Losing the Owner Password. If you apply AES-256 and forget the password, the document is mathematically gone forever alongside your data. There is no backdoor, no Adobe master override, and no recovery tool on Earth that can reverse AES-256 without the key.
- Encrypting Metadata on public sites. Publishing secure research reports on an indexable website and leaving
/EncryptMetadata true. Search engine crawlers (Googlebot) cannot read encrypted strings. Your document will fail to rank in searches entirely because Google cannot parse the author or title.
Frequently Asked Questions
The User password is required simply to view the document contents. The Owner password proves you are the administrator; it bypasses all DRM restrictions (like copy/print prevention) and allows you to strip the security off the file completely.
A Crypt Filter maps a specific encryption standard (like AESV2) to specific parts of the PDF document. It allows granular security, such as leaving the main text unencrypted to be searchable while heavily encrypting sensitive embedded files attached to the document.
No. If the user can *view* the file, the file must be decrypted in their computer's RAM. The viewer software is operating on an honor system to enforce the `/P` (Permissions) rules. Many third-party apps ignore these rules entirely and allow printing or copying.
If set to 'false', the XMP metadata (title, keywords, author) is left completely unencrypted while the main content is locked behind AES. This allows search engines and database systems to organize the secure file without knowing the password.
Under modern cryptography, AES-256 (Revision 6) is mathematically impossible to brute force. The only way an attacker accesses the data is through phishing, keyloggers, or guessing a very weak password (like "password123").
40-bit RC4 was designed for 1990s processors under strict export regulations. A modern desktop CPU can brute-force the entire 40-bit keyspace and decrypt the document in seconds regardless of how complex your password was.
Secure Your Documents with AES-256
PDFlyst provides enterprise-grade encryption tools to apply strict passwords, block printing, and prevent data extraction instantly.
Encrypt PDF Securely