Encrypted Files vs Password-Protected Files: What's Actually Secure?
You've seen it a thousand times: "This PDF is password protected" or "This ZIP file is encrypted." You feel safe. But should you?
The short answer: No. Most password-protected files are using outdated, weak encryption that can be cracked in minutes.
What "password protected" usually means
When you password-protect a PDF or ZIP file using standard software, here's what actually happens:
PDFs use the "Standard Security Handler" — typically RC4 (broken since 2015) or AES-128 in CBC mode without authentication. Modern tools can crack these in seconds to minutes depending on password complexity.
ZIP files use the original ZipCrypto encryption by default. This algorithm has been broken since 1994. Tools like John the Ripper can crack ZipCrypto passwords in minutes using known-plaintext attacks. Even when ZIPs use AES-256 (WinRAR 5.0+), the encryption is only as strong as the password — which is often weak because humans can't remember strong ones.
Microsoft Office uses AES-256 in ECB mode (not GCM) — which means identical plaintext blocks produce identical ciphertext, leaking patterns.
Why this is dangerous
Password-protected files give a false sense of security. People believe their file is safe and share it freely — but the encryption is so weak that a determined attacker can read it in minutes.
Common attack scenarios:
- Intercepting an email attachment — cracked in seconds
- Finding a "lost" USB drive — password extracted in minutes
- Recovering files from old computers — passwords cracked automatically
- Brute-forcing a 6-character password — done in under an hour
What real encryption looks like
True encryption has three properties that password-locked files lack:
1. Strong cipher — AES-256-GCM or ChaCha20-Poly1305. Both have been independently audited and are used by governments and militaries worldwide.
2. Authenticated encryption — GCM mode includes a cryptographic tag that detects tampering. If anyone modifies the file (even one byte), decryption fails immediately.
3. Random keys, not passwords — A 256-bit key (77-digit number) is cryptographically random. There's no password for an attacker to guess — they'd need to break AES itself, which is computationally infeasible.
How FastDDL is different
FastDDL uses AES-256-GCM with a random 256-bit key generated in your browser. The key is shown to you once in a human-readable format — but even if an attacker obtains the key, they can't crack it. The only way to read your file is to have the exact key.
There's no "password recovery" because we don't have the key. There's no "brute force" because the key space is 2^256 — more than the number of atoms in the observable universe.
When password-locked files are okay
Password-protected files are fine when:
- The password is very long (20+ random characters)
- The data has low value (not worth attacking)
- It's a casual obstacle, not real protection
- You use modern tools with AES-256 (7-Zip, Keka, WinRAR 5+)
For anything sensitive — financial data, medical records, source code, legal documents — use proper encryption like FastDDL.
The bottom line
Don't confuse "password-protected" with "encrypted." They're different. For real security, use modern authenticated encryption (AES-GCM or ChaCha20-Poly1305) with random keys — exactly what FastDDL does.