See the test files and checks
This public study records what was tested, how each result was verified and which parts remain configuration only. It is a transparent fixture study for format compatibility, with each result tied to a named public file.
A local fixture result is evidence of the check, not a recovery promise
The study uses owned public fixtures with known positive candidates and negative controls. A passed local check confirms the documented method worked on that fixture; it does not predict the outcome for an unrelated file.
Study scope
A small, inspectable record
The counts below come directly from the research record. Read them alongside the fixture rows and method notes; an aggregate count without the underlying file and check is not enough to assess evidence.
demo-public-2026!Method and tools
- 1Create synthetic public content and encrypt it with the disclosed demonstration passwords.
- 2Open or decrypt each file with the correct password using a local parser and verify the expected content or container.
- 3Reject a deliberately wrong password as a negative control; separately test the empty user password on the permissions-only PDF.
- 4Run the local service detector and extractor against the same immutable files, without submitting a production job.
- 5Publish the fixture SHA-256, detected profile, outcomes and a portable reproduction script. No GPU speed or customer win rate is measured.
Tool versions recorded in the study
- Python 3.11.9
- pyzipper 0.3.6
- py7zr 1.1.0
- pypdf 6.7.1
- msoffcrypto-tool 6.0.0
- python-docx 1.2.0
- openpyxl 3.1.5
- olefile 0.47
Evidence legend
- Configured route
- A route is defined for the format or protection profile.
- Locally verified fixture
- A known-password check passed on the linked public dummy file.
- Decrypt verified
- The fixture was opened or decrypted locally with its known password.
- Extractor checked
- A format extractor check ran; this is separate from end-to-end recovery.
Public fixture record
What was actually checked
Each row identifies a public dummy fixture, its profile and the checks used: a known-password local verification and a negative control. Where the record includes them, decrypt verification and extractor checks are shown as separate states.
| Fixture | Family / profile | SHA-256 | Checks | Result |
|---|---|---|---|---|
zipcrypto zipcrypto_public.zip | archive ZIP ZipCrypto | 8918d87dd875dd5e5e744b5a5942a203f3d4bffa71ca9309b398d80c4471084c |
| Fixture result: verified |
zip_aes256 zip_aes256_public.zip | archive ZIP WinZip AES-256 | 0ec0f0789af7b5266cfaa741485cf269c8c4507a3d9d19fcf21933bce63753d8 |
| Fixture result: verified |
sevenzip_aes sevenzip_aes_public.7z | archive 7z AES-256 with encrypted headers | 5deb291059740dd33e09a9520bc7923e0ad89726d7ed1e845fc09d2e73258392 |
| Fixture result: verified |
pdf_open pdf_open_password_public.pdf | pdf PDF open/user password (RC4-128 via pypdf) | 550e5f3afdf4ee36a56adb7d4e1dfae4cf7e88a752012cc02b0c1208400bb6a8 |
| Fixture result: verified |
pdf_owner_only pdf_owner_only_public.pdf | pdf PDF owner-only password with empty user password | 756114290f03957aece2d054eac98a42db03874824b4850719d77a3131b7a6cd |
| Fixture result: verified |
docx modern_password_public.docx | office OOXML DOCX — Office 2007 Standard encryption (AES-128) | d56ce2658767e53bc303e3a7b4653b3993528ac5fac452613ec0832dcf861d88 |
| Fixture result: verified |
xlsx modern_password_public.xlsx | office OOXML XLSX — Office 2007 Standard encryption (AES-128) | a1a078ddd6849c403076bebd492cabe2a3d621107111a94d09513f25d2620675 |
| Fixture result: verified |
pptx modern_password_public.pptx | office OOXML PPTX — Office 2007 Standard encryption (AES-128) | 13638ed5ded86fb44ba48d38e86425189bbf8c2d6fe41fd3bf4cc7b2692b8b4b |
| Fixture result: verified |
Last verified: . These are public dummy fixtures and known-password local checks; they do not predict the outcome for another file.
Download and reproduce the study
The files below contain the owned public fixture record, exact method notes and machine-readable results. They are intended for inspection and local reproduction.
Read the boundaries clearly
The fixtures are owned dummy data with known local answers. They help validate a format parser and candidate verification method. They do not measure production throughput, recovery timing or the chance of finding an unknown password.
Frequently Asked Questions
Next step
Have an authorised file to assess?
Use the fixture study to understand the evidence, then identify your own file’s protection before choosing a route.