docs
This commit is contained in:
parent
659b5ba508
commit
89a8af2aa1
@ -354,3 +354,4 @@ The project includes comprehensive tests:
|
||||
./test_secret_manager.sh # Full integration test suite
|
||||
go test ./... # Unit tests
|
||||
```
|
||||
|
||||
|
8
TODO.md
8
TODO.md
@ -16,6 +16,14 @@ This document outlines the bugs, issues, and improvements that need to be addres
|
||||
|
||||
### Core Functionality Bugs
|
||||
|
||||
- [ ] Multiple vaults using the same mnemonic will derive the same long-term
|
||||
keys. Adding additional vaults with the same mnemonic should increment the
|
||||
index value used. The mnemonic should be double sha256 hashed and the hash
|
||||
value stored in the vault metadata along with the index value (starting at zero)
|
||||
and when additional vaults are added with the same mnemonic (as determined by
|
||||
hash) then the index value should be incremented. The README should be updated
|
||||
to document this behavior.
|
||||
|
||||
- [ ] **Directory structure inconsistency**: The README and test script reference different directory structures:
|
||||
- Current code uses `unlock.d/` but documentation shows `unlock-keys.d/`
|
||||
- Secret files use inconsistent naming (`secret.age` vs `value.age`)
|
||||
|
Loading…
Reference in New Issue
Block a user