[rpcwallet] Clamp walletpassphrase value at 100M seconds
Larger values seem to trigger a bug on macos+libevent (resulting in the rpc server stopping).
This commit is contained in:
parent
1d540046fe
commit
662d19ff72
2 changed files with 10 additions and 9 deletions
test/functional
|
@ -64,14 +64,15 @@ class WalletEncryptionTest(BitcoinTestFramework):
|
|||
assert_raises_rpc_error(-8, "Timeout cannot be negative.", self.nodes[0].walletpassphrase, passphrase2, -10)
|
||||
# Check the timeout
|
||||
# Check a time less than the limit
|
||||
expected_time = int(time.time()) + (1 << 30) - 600
|
||||
self.nodes[0].walletpassphrase(passphrase2, (1 << 30) - 600)
|
||||
MAX_VALUE = 100000000
|
||||
expected_time = int(time.time()) + MAX_VALUE - 600
|
||||
self.nodes[0].walletpassphrase(passphrase2, MAX_VALUE - 600)
|
||||
actual_time = self.nodes[0].getwalletinfo()['unlocked_until']
|
||||
assert_greater_than_or_equal(actual_time, expected_time)
|
||||
assert_greater_than(expected_time + 5, actual_time) # 5 second buffer
|
||||
# Check a time greater than the limit
|
||||
expected_time = int(time.time()) + (1 << 30) - 1
|
||||
self.nodes[0].walletpassphrase(passphrase2, (1 << 33))
|
||||
expected_time = int(time.time()) + MAX_VALUE - 1
|
||||
self.nodes[0].walletpassphrase(passphrase2, MAX_VALUE + 1000)
|
||||
actual_time = self.nodes[0].getwalletinfo()['unlocked_until']
|
||||
assert_greater_than_or_equal(actual_time, expected_time)
|
||||
assert_greater_than(expected_time + 5, actual_time) # 5 second buffer
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue