Merge #16394: Allow createwallet to take empty passwords to make unencrypted wallets
pull/764/headc5d3787367
Allow createwallet to take empty passwords to make unencrypted wallets (Andrew Chow) Pull request description: Allow createwallet to take the empty string as a password and interpret that as leaving the wallet unencrypted. Also warn when that happens. This fixes a bug where it was not possible to use the `avoid_reuse` option for new unencrypted wallets without using named arguments.Thus this allows more `createwallet` options to be added that can be set on unencrypted wallets when using positional arguments. ACKs for top commit: jnewbery: code review ACKc5d3787367
meshcollider: re-utACKc5d3787367
ryanofsky: utACKc5d3787367
. Changes since last review are rebasing, concatenating warning strings to avoid discarding warnings, adding release notes, and choosing an unambiguous wallet name for the test. Tree-SHA512: 146737a728dd614ba94d4b166b27e8c9e195badd1709ccab2315afe59176d9b493dfba9b61c3ed81090f059c7e464d709deb06d99451b9a3fff667f527d6f7c9
commit
6841b01340
@ -0,0 +1,4 @@
|
||||
RPC changes
|
||||
-----------
|
||||
`createwallet` now returns a warning if an empty string is used as an encryption password, and does not encrypt the wallet, instead of raising an error.
|
||||
This makes it easier to disable encryption but also specify other options when using the `bitcoin-cli` tool.
|
Loading…
Reference in new issue