Skip to content

bug(sandbox): signal and scheduling mediation results are logged as denied network notifications #5705

Open

Description

@EmilienM

User Story

I run OpenShell sandboxes with the Podman and Kubernetes drivers and I work on the sandbox isolation core. This came out of the review of #5212. I found it by reading the code and have not hit it in production.

Problem Statement

crates/openshell-sandbox/src/network_broker.rs logs every error from dispatch_notification with one WARN: sandbox network notification denied (tid=..., syscall=...). The broker also mediates kill, tkill, rt_sigqueueinfo, and (with #5212) prlimit64, sched_set*, and setpriority, so that line now mixes two different things for calls that are not network events:

  • Usage errors the kernel would return natively, such as ESRCH for a target that already exited or EINVAL for a bad signal number or selector. These are not denials.
  • Policy decisions: EPERM for the trusted sandbox leader, for a target outside the caller's thread group, or for PRIO_PGRP/PRIO_USER. These are observable sandbox behavior and AGENTS.md asks for an OCSF event, but none is emitted.

Impact / Why This Matters

Operators see "network notification denied" warnings for ordinary process races (#3526 measured kill returning ESRCH in healthy pods), while a workload that tries to signal or reschedule a process it must not touch leaves no structured event for security tooling. There is no workaround short of parsing the errno out of the warning text.

Acceptance Criteria

  • Native usage errors from signal and scheduling mediation are logged below WARN and are not called "network" or "denied".
  • EPERM denials from process_signal and process_sched emit an OCSF event (process activity, severity Medium) that names the syscall, the caller, and the target.
  • Network denials keep their current events.

Reproduction Steps

Not run; from the code. Inside a sandbox, python3 -c 'import os; os.kill(4000000, 0)' fails with ESRCH as it would natively, and the sandbox log gains a sandbox network notification denied warning for the kill syscall.

Environment

  • OpenShell: main at fea144c45
  • OS: Fedora 45, Linux 7.2.15
  • Deployment: Podman driver (local gateway)

Related: #5130 reports the same log line for an in-progress nonblocking connect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    state:triage-neededOpened without agent diagnostics and needs triage

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions