diff options
| author | fanquake <fanquake@gmail.com> | 2023-05-04 12:07:26 +0100 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2023-06-16 10:38:19 +0100 |
| commit | 32e2ffc39374f61bb2435da507f285459985df9e (patch) | |
| tree | 44103a701bd14b0c77163db5d557215d40842210 /test/functional/feature_startupnotify.py | |
| parent | b3db18a0126bc4181d2a0880c27f45d203d06179 (diff) | |
Remove the syscall sandbox
After initially being merged in #20487, it's no-longer clear that an
internal syscall sandboxing mechanism is something that Bitcoin Core
should have/maintain, especially when compared to better
maintained/supported alterantives, i.e firejail.
Note that given where it's used, the sandbox also gets dragged into the
kernel.
There is some related discussion in #24771.
This should not require any sort of deprecation, as this was only ever
an opt-in, experimental feature.
Closes #24771.
Diffstat (limited to 'test/functional/feature_startupnotify.py')
| -rwxr-xr-x | test/functional/feature_startupnotify.py | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/test/functional/feature_startupnotify.py b/test/functional/feature_startupnotify.py index ff5272b281..5c00984404 100755 --- a/test/functional/feature_startupnotify.py +++ b/test/functional/feature_startupnotify.py @@ -18,7 +18,6 @@ FILE_NAME = "test.txt" class StartupNotifyTest(BitcoinTestFramework): def set_test_params(self): self.num_nodes = 1 - self.disable_syscall_sandbox = True def run_test(self): tmpdir_file = os.path.join(self.options.tmpdir, NODE_DIR, FILE_NAME) |