docs(12-user-key-input): create phase plan
This commit is contained in:
@@ -216,3 +216,14 @@ Phases execute in numeric order: 1 -> 2 -> 3 -> 4 -> 5 -> 6 -> 7 -> 8 -> 9 -> 10
|
||||
| 9. Kotlin Decoder Update | v1.1 | 0/1 | Not started | - |
|
||||
| 10. Shell Decoder Update | v1.1 | 0/TBD | Not started | - |
|
||||
| 11. Directory Cross-Validation | v1.1 | 0/TBD | Not started | - |
|
||||
|
||||
### Phase 12: User Key Input
|
||||
|
||||
**Goal:** Replace hardcoded encryption key with user-specified key input: `--password` (interactive prompt or CLI value, derived via Argon2id), `--key` (raw 64-char hex), `--key-file` (read 32 bytes from file). All three methods produce a 32-byte AES-256 key passed through pack/unpack/inspect.
|
||||
**Requirements**: KEY-01, KEY-02, KEY-03, KEY-04, KEY-05, KEY-06, KEY-07
|
||||
**Depends on:** Phase 11
|
||||
**Plans:** 2 plans
|
||||
|
||||
Plans:
|
||||
- [ ] 12-01-PLAN.md -- CLI key args (--key, --key-file, --password), refactor archive.rs to accept key parameter, update all tests
|
||||
- [ ] 12-02-PLAN.md -- Argon2id KDF, rpassword interactive prompt, salt storage in archive format (flags bit 4)
|
||||
|
||||
Reference in New Issue
Block a user