Wladimir J. van der Laan
362e901a17
Merge #18466: rpc: fix invalid parameter error codes for {sign,verify}message RPCs
a5cfb40e27bd281354bd0d14d91f83efb6bfce9f doc: release note for changed {sign,verify}message error codes (Sebastian Falbesoner)
9e399b9b2d386b28c0c0ff59fc75d31dbec31d9c test: check parameter validity in rpc_signmessage.py (Sebastian Falbesoner)
e62f0c71f10def124b1c1219d790cef246a32c3e rpc: fix {sign,message}verify RPC errors for invalid address/signature (Sebastian Falbesoner)
Pull request description:
RPCs that accept address parameters usually return the intended error code `RPC_INVALID_ADDRESS_OR_KEY` (-5) if a passed address is invalid. The two exceptions to the rule are `signmessage` and `verifymessage`, which return `RPC_TYPE_ERROR` (-3) in this case instead. Oddly enough `verifymessage` returns `RPC_INVALID_ADDRESS_OR_KEY` when the _signature_ was malformed, where `RPC_TYPE_ERROR` would be more approriate.
This PR fixes these inaccuracies and as well adds tests to `rpc_signmessage.py` that check the parameter validity and error codes for the related RPCs `signmessagewithprivkey`, `signmessage` and `verifymessage`.
master branch:
```
$ ./bitcoin-cli signmessage invalid_addr message
error code: -3
error message:
Invalid address
$ ./bitcoin-cli verifymessage invalid_addr dummy_sig message
error code: -3
error message:
Invalid address
$ ./bitcoin-cli verifymessage 12c6DSiU4Rq3P4ZxziKxzrL5LmMBrzjrJX invalid_sig message
error code: -5
error message:
Malformed base64 encoding
```
PR branch:
```
$ ./bitcoin-cli signmessage invalid_addr message
error code: -5
error message:
Invalid address
$ ./bitcoin-cli verifymessage invalid_addr dummy_sig message
error code: -5
error message:
Invalid address
$ ./bitcoin-cli verifymessage 12c6DSiU4Rq3P4ZxziKxzrL5LmMBrzjrJX invalid_sig message
error code: -3
error message:
Malformed base64 encoding
```
ACKs for top commit:
laanwj:
Code review ACK a5cfb40e27bd281354bd0d14d91f83efb6bfce9f
meshcollider:
utACK a5cfb40e27bd281354bd0d14d91f83efb6bfce9f
Tree-SHA512: bae0c4595a2603cea66090f6033785601837b45fd853052312b3a39d8520566c581994b68f693dd247c22586c638c3b7689c849085cce548cc36b9bf0e119d2d
2021-03-01 11:45:42 +01:00
..
2021-02-09 15:00:02 +01:00
2021-02-01 15:17:28 +01:00
2021-01-17 18:10:20 +01:00
2021-02-01 22:43:17 +13:00
2021-02-01 22:43:17 +13:00
2020-05-28 02:13:19 -04:00
2020-07-09 13:07:37 +02:00
2020-12-31 09:45:41 +01:00
2020-12-04 11:03:28 -04:00
2020-12-04 11:03:28 -04:00
2020-12-16 12:33:06 -05:00
2020-12-16 12:33:06 -05:00
2021-02-23 14:34:31 +01:00
2021-02-23 14:34:32 +01:00
2021-02-23 14:34:32 +01:00
2021-02-23 14:34:32 +01:00
2021-01-07 09:05:09 +01:00
2020-12-31 09:45:41 +01:00
2021-02-23 11:05:13 -08:00
2021-02-23 14:34:30 +01:00
2021-01-19 19:04:45 +08:00
2021-01-15 22:48:15 +01:00
2020-12-31 09:45:41 +01:00
2021-02-23 08:51:01 +01:00
2021-02-23 14:34:31 +01:00
2021-02-23 14:34:30 +01:00
2021-03-01 11:45:42 +01:00
2020-09-22 20:49:30 +02:00
2020-12-04 11:03:28 -04:00
2020-07-26 20:22:45 -04:00
2021-02-23 14:34:32 +01:00
2021-02-23 14:34:31 +01:00
2020-12-04 11:03:28 -04:00
2021-01-04 12:31:31 +08:00
2021-02-23 14:34:32 +01:00
2021-02-23 14:34:31 +01:00
2021-02-09 19:01:15 +01:00
2020-11-18 11:55:43 -05:00
2021-01-21 19:30:34 +01:00
2021-01-21 19:30:34 +01:00
2020-12-31 09:45:41 +01:00
2021-02-23 14:34:30 +01:00