diff options
| author | MarcoFalke <*~=`'#}+{/-|&$^_@721217.xyz> | 2023-01-25 15:32:31 +0100 |
|---|---|---|
| committer | MarcoFalke <*~=`'#}+{/-|&$^_@721217.xyz> | 2023-01-25 15:32:41 +0100 |
| commit | 0486148f75547232377d344b37a542cea81023d9 (patch) | |
| tree | 541a0206898c788ecef11fff97e26ee69297f69b /test/functional/rpc_blockchain.py | |
| parent | f703c79ad729e1036431b20c8cb03f5b24c11815 (diff) | |
| parent | b9d567454159f062ce84353f5821d6e6daf433bd (diff) | |
Merge bitcoin/bitcoin#26829: init: Remove unnecessary sensitive flag from rpcbind
b9d567454159f062ce84353f5821d6e6daf433bd init: Remove sensitive flag from rpcbind (Andrew Chow)
Pull request description:
`-rpcbind` is currently flagged as a sensitive option which means that its value will be masked when the command line args are written to the debug.log file. However this is not useful as if `rpcbind` is actually activated, the bound IP addresses will be written to the log anyways. The test `feature_config_args.py` did not catch this contradiction as the test node was not started with `rpcallowip` and so `rpcbind` was not acted upon.
This also brings `rpcbind` inline with `bind` as that is not flagged as sensitive either.
ACKs for top commit:
Sjors:
re-utACK b9d567454159f062ce84353f5821d6e6daf433bd
willcl-ark:
ACK b9d5674
theStack:
ACK b9d567454159f062ce84353f5821d6e6daf433bd
Tree-SHA512: 50ab5ad2e18ae70649deb1ac429d404b5f5c41f32a4943b2041480580152df22e72d4aae493379d0b23fcb649ab342376a82119760fbf6dfdcda659ffd3e244a
Diffstat (limited to 'test/functional/rpc_blockchain.py')
0 files changed, 0 insertions, 0 deletions