aboutsummaryrefslogtreecommitdiff
path: root/test/functional/rpc_signer.py
diff options
context:
space:
mode:
authorfanquake <fanquake@gmail.com>2023-05-04 12:07:26 +0100
committerfanquake <fanquake@gmail.com>2023-06-16 10:38:19 +0100
commit32e2ffc39374f61bb2435da507f285459985df9e (patch)
tree44103a701bd14b0c77163db5d557215d40842210 /test/functional/rpc_signer.py
parentb3db18a0126bc4181d2a0880c27f45d203d06179 (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/rpc_signer.py')
-rwxr-xr-xtest/functional/rpc_signer.py3
1 files changed, 0 insertions, 3 deletions
diff --git a/test/functional/rpc_signer.py b/test/functional/rpc_signer.py
index 4300190387..5ba0d35835 100755
--- a/test/functional/rpc_signer.py
+++ b/test/functional/rpc_signer.py
@@ -27,9 +27,6 @@ class RPCSignerTest(BitcoinTestFramework):
def set_test_params(self):
self.num_nodes = 4
- # The experimental syscall sandbox feature (-sandbox) is not compatible with -signer (which
- # invokes execve).
- self.disable_syscall_sandbox = True
self.extra_args = [
[],