| commit | 7b6e8bc4424006119dc537699c8b3b3121e0b3c3 | |
| author | Wladimir J. van der Laan <laanwj@gmail.com> | |
| Tue, 18 Jul 2017 07:30:24 +0000 (18 09:30 +0200) | ||
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | |
| Tue, 18 Jul 2017 07:30:33 +0000 (18 09:30 +0200) | ||
| tree | 3a507702c01d8c7f89a9414c625e9fd6c2d5337f | treesnapshot (tar.gz zip) |
| parent | 81560b07ce8a14fb3a965a8f231545f05d8d7768 | commitdiff |
| parent | 1fc8c3de0cff2971cc1f9903bfc3d03a982f2fab | commitdiff |
Merge #10795: No longer ever reuse keypool indexes
1fc8c3d No longer ever reuse keypool indexes (Matt Corallo)
Pull request description:
This fixes an issue where you could reserve a keypool entry, then
top up the keypool, writing out a new key at the given index, then
return they key from the pool. This isnt likely to cause issues,
but given there is no reason to ever re-use keypool indexes
(they're 64 bits...), best to avoid it alltogether.
Builds on #10235, should probably get a 15 tag.
Tree-SHA512: c13a18a90f1076fb74307f2d64e9d80149811524c6bda259698ff2c65adaf8c6c3f2a3a07a5f4bf03251bc942ba8f5fd33a4427aa4256748c40b062991682caf
1fc8c3d No longer ever reuse keypool indexes (Matt Corallo)
Pull request description:
This fixes an issue where you could reserve a keypool entry, then
top up the keypool, writing out a new key at the given index, then
return they key from the pool. This isnt likely to cause issues,
but given there is no reason to ever re-use keypool indexes
(they're 64 bits...), best to avoid it alltogether.
Builds on #10235, should probably get a 15 tag.
Tree-SHA512: c13a18a90f1076fb74307f2d64e9d80149811524c6bda259698ff2c65adaf8c6c3f2a3a07a5f4bf03251bc942ba8f5fd33a4427aa4256748c40b062991682caf