{"version":"2.1.223","anchor":"sandbox-now-fails-loudly-when-proc-self-exe-cannot-be-opened","canonical_anchor":"sandbox-now-fails-loudly-when-proc-self-exe-cannot-be-opened","heading":"Sandbox now fails loudly when \/proc\/self\/exe cannot be opened","tier":"notice","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/sandbox-now-fails-loudly-when-proc-self-exe-cannot-be-opened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Sandbox now fails loudly when \/proc\/self\/exe cannot be opened\n\nOn Linux, if the sandbox can't set itself up it now stops instead of silently running half-protected.\n\n**What**\n\nThe Linux seccomp helper used to log an error and return undefined, letting startup continue with the sandbox half-configured. It now throws.\n\n**Details**\n\n- The error is still reported, then constructed and thrown so the caller cannot proceed.\n- The message text was rewritten to name the embedded apply-seccomp helper.\n- Only on the Linux seccomp sandbox path.\n\n**Evidence**\n\n`sandbox: failed to open \/proc\/self\/exe`\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}