feat(cli): read the wallet password from env, stdin or a prompt
The password no longer has to be a command-line argument: it can come from --password-env, --password-stdin or a no-echo prompt (--password still works but warns). Plaintext storage is now an explicit opt-in (--no-encryption) instead of the result of a forgotten flag. See ADR 0038.
This commit is contained in:
1 parent
eca4d4ac0c
commit
92fd783658
8 files changed
+342
-38
No files matched your search
@@ -7,6 +7,16 @@ release and covers the full history from the initial commit.
|
||||
|
||||
## [Unreleased]
|
||||
|
||||
### Changed
|
||||
|
||||
- **CLI (behaviour change):** the wallet password no longer has to be a command-line argument.
|
||||
It can come from `--password-env NAME`, `--password-stdin`, or a no-echo terminal prompt
|
||||
(with a confirmation when creating); with no terminal and no password the command fails
|
||||
instead of hanging. `--password P` still works but prints a warning on stderr (shell history,
|
||||
process list). Plaintext storage is now an explicit opt-in: `create`/`restore*` without a
|
||||
password and without `--no-encryption` fail, where before they silently wrote the seed
|
||||
unencrypted. Scripts that relied on omitting `--password` must add `--no-encryption`.
|
||||
|
||||
### Security
|
||||
|
||||
- Private keys are no longer precomputed for every address in the UI. Address rows and the
|
||||
|
||||
Reference in new issue
Block a user