Skip to content

[CWS] Add host user namespace fields to capability nodes - #528

Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit into
masterfrom
yoanngh/cws-capability-node-host-userns
Sep 30, 2026
Merged

gh-worker-dd-mergequeue-cf854d[bot] merged 1 commit into
masterfrom
yoanngh/cws-capability-node-host-userns

Conversation

@YoannGh

@YoannGh YoannGh commented Sep 30, 2026

Copy link
Copy Markdown
Contributor

What does this PR do?

Adds two fields to the CWS activity dump capability node, recording whether a capability was checked against, and obtained from, the initial user namespace.

Motivation

The Agent now reports that distinction on capability events, because those capabilities stop being granted once a workload runs in its own user namespace. Activity dumps and security profiles need the same two fields to carry it.

Additional Notes

Both fields are new and additive, so older consumers keep decoding these nodes unchanged.

Describe how to test/QA your changes

Nothing to exercise here on its own; the Agent side is validated against a build of this branch.

Lets activity dumps record which capabilities a process obtained from the
initial user namespace, alongside whether it obtained them at all.
@YoannGh YoannGh changed the title cws: add initial user namespace fields to capability nodes [CWS] Add host user namespace fields to capability nodes Sep 30, 2026
@YoannGh
YoannGh marked this pull request as ready for review September 30, 2026 12:08
@YoannGh
YoannGh requested a review from a team as a code owner September 30, 2026 12:08
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 30, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-30T12:13:47.926639Z b9d8367 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants