6 commits

Author	SHA1	Message	Date
Daniel Kraft	57889e688d	bitcoin-tx: Stricter check for valid integers ... Just calling atoi to convert strings to integers does not check for valid integers very thoroughly; in particular, it just ignores everything starting from the first non-numeral character. Even a string like "foo" is fine and silently returns 0. This meant that bitcoin-tx would not fail if such a string was passed in various places where an integer is expected (like the locktime or an input/output index); this means that it would, for instance, silently accept a typo and interpret it in an unexpected way. In this change, we use ParseInt64 for parsing strings to integers, which actually verifies that the full string is valid as number. New tests in the bitcoin-util-test cover the new error paths.	2018-07-07 14:25:09 +02:00
practicalswift	d27327c79a	Fix typos	2018-03-21 10:54:17 +01:00
Matt Corallo	28d4542a0a	Disallow uncompressed pubkeys in bitcoin-tx [multisig] output adds	2017-09-20 23:29:59 -04:00
John Newbery	19ecd1e2e1	Add tests for bitcoin-tx input checking	2017-03-30 16:37:53 -04:00
John Newbery	21704f6334	Check stderr when testing bitcoin-tx	2017-03-30 16:37:53 -04:00
John Newbery	63d66ba20a	Move src/test/bitcoin-util-test.py to test/util/bitcoin-util-test.py	2017-03-20 10:40:31 -04:00

Renamed from src/test/data/bitcoin-util-test.json (Browse further)