diff options
| author | Wladimir J. van der Laan <laanwj@protonmail.com> | 2020-05-04 16:30:35 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@protonmail.com> | 2020-05-04 16:31:07 +0200 |
| commit | b549cb1bd2cc4c6d7daeccdd06915bec590e90ca (patch) | |
| tree | af04fed2e419d528616caa8ea9198b5a44bbffe8 /test/functional/feature_help.py | |
| parent | 23c926d859c60379fba97ad106978077a317841f (diff) | |
| parent | f85203097f78d9daa1d35c4097a80beab31da2a4 (diff) | |
Merge #18443: lockedpool: avoid sensitive data in core files (FreeBSD)
f85203097f78d9daa1d35c4097a80beab31da2a4 lockedpool: avoid sensitive data in core files (FreeBSD) (Vasil Dimov)
Pull request description:
This is a followup to
23991ee53 / https://github.com/bitcoin/bitcoin/pull/15600
to also use madvise(2) on FreeBSD to avoid sensitive data allocated
with secure_allocator ending up in core files in addition to preventing
it from going to the swap.
ACKs for top commit:
sipa:
ACK f85203097f78d9daa1d35c4097a80beab31da2a4 if someone verifies this works as intended on *BSD.
laanwj:
ACK f85203097f78d9daa1d35c4097a80beab31da2a4
practicalswift:
Code-review ACK f85203097f78d9daa1d35c4097a80beab31da2a4 assuming a reviewer with FreeBSD access verifies that the PR goal is achieved :)
Tree-SHA512: 2e6d4ab6a9fbe18732c8ba530eacc17f58128c97140758b80c905b5b838922a2bcaa5f9abc45ab69d5a1a2baa0cba322f006048b60a877228e089c7e64dadd2a
Diffstat (limited to 'test/functional/feature_help.py')
0 files changed, 0 insertions, 0 deletions