Skip to content

docs: RFC for seccomp-notify network enforcement#14

Closed
Ladas wants to merge 1 commit into
feat/platform-mode-v2from
feat/seccomp-notify-rfc
Closed

docs: RFC for seccomp-notify network enforcement#14
Ladas wants to merge 1 commit into
feat/platform-mode-v2from
feat/seccomp-notify-rfc

Conversation

@Ladas

@Ladas Ladas commented Jun 12, 2026

Copy link
Copy Markdown

Summary

Design-only RFC for kernel-level domain/IP filtering using seccomp-notify
(SECCOMP_RET_USER_NOTIF). The supervisor intercepts connect() at the
syscall dispatch boundary, evaluates against a DNS-pinned allowlist, and
performs on-behalf-of operations via pidfd_getfd().

This is a design document, not an implementation. The RFC lives at
docs/rfcs/seccomp-notify-network-enforcement.md.

Relationship to other PRs

These are complementary, not competing. Landlock port restriction forces traffic
through the proxy. seccomp-notify provides domain filtering at the syscall level
when no proxy is available.

Effort estimate

~300-500 LOC, 2-3 weeks for implementation (separate PR).

Assisted-By: Claude Code

Design proposal for kernel-level domain/IP filtering using
SECCOMP_RET_USER_NOTIF. Alternative to Landlock TCP port restriction
for standalone deployments without a proxy.

Implementation: ~300-500 LOC, 2-3 weeks. All kernel features
available on RHEL 9 / OpenShift 4.18.

Ref: NVIDIA#899
@Ladas Ladas closed this Jun 12, 2026
@Ladas Ladas deleted the feat/seccomp-notify-rfc branch June 12, 2026 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant