Expand description
Key acquisition for the DeDRM schemes.
Two kinds of key source, mirroring the Python tools:
- Offline generators (pure crypto, reproducible anywhere): PID encoders
(
pid), B&N name+CC keygen (ignoble), eReader name+CC key (ereader), Kobo device-key derivation (kobo). These are implemented. - Platform extraction (reads local DRM-app state — registry/DPAPI,
plists, SQLite):
kindle,adobe. These are stubbed and are the parts that require a specific host OS + user profile.
Reference: docs/DEDRM_SCHEMES.md §2.5, §4, §6, §7.2, §8.2, §9.2.
Re-exports§
pub use error::KeyError;
Modules§
- adobe
- Adobe ADEPT user-key extraction (the RSA private key DER, “adobekey.der”).
- ereader
- eReader offline user-key derivation from name + credit-card number.
- error
- ignoble
- Barnes & Noble “ignoble” offline key generation from account name + card.
- kindle
- Kindle device/account key extraction (
.kinf/.k4i, Android, eInk serials). - kobo
- Kobo user-key derivation and on-host discovery.
- pid
- Kindle PID generation & encoding (Mobipocket / Topaz / KFX).
Structs§
- KeyStore
- All candidate keys gathered for a decryption attempt. Schemes brute-force the relevant bucket against the book. Mirrors the plugin’s prefs buckets.