Skip to content

Add SECURITY.md#697

Open
jolorunyomi wants to merge 1 commit into
mainfrom
security/add-security-md
Open

Add SECURITY.md#697
jolorunyomi wants to merge 1 commit into
mainfrom
security/add-security-md

Conversation

@jolorunyomi
Copy link
Copy Markdown

This PR adds a SECURITY.md file to the repository, outlining the security policies and procedures for reporting vulnerabilities. This is part of our effort to enhance the security posture of our projects and ensure that we have a clear process for handling security issues.

@jolorunyomi jolorunyomi requested a review from a team as a code owner May 13, 2026 01:45
@jolorunyomi jolorunyomi requested review from KyleFromNVIDIA and removed request for a team May 13, 2026 01:45
@jolorunyomi jolorunyomi added the non-breaking Introduces a non-breaking change label May 13, 2026
@msarahan msarahan requested review from msarahan and removed request for KyleFromNVIDIA May 13, 2026 13:41
@msarahan msarahan added the improvement Improves an existing functionality label May 13, 2026
Comment thread SECURITY.md
Comment on lines +94 to +96
container. The `main` devcontainer additionally sets
`"containerUser": "root"`, so post-attach code runs as root inside
the container.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, containerUser defines the user during the image build, not the user the container is run as. The container runs as the unprivileged coder user, including all lifecycle scripts.

Comment thread SECURITY.md
Comment on lines +128 to +135
2. **`containerUser: root` in the main devcontainer.**
The base `image/.devcontainer/devcontainer.json` declares
`"containerUser": "root"`. Code running as root inside the
container can write to mounted host paths with uid 0 ownership,
which surprises subsequent host-side tooling and (depending on
Docker rootless / rootful configuration) can produce files the
host user cannot remove without `sudo`. Consumer configs that
override this should be reviewed against their feature set.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope

Comment thread SECURITY.md
Comment on lines +211 to +214
on disk (subject to Docker's user namespace configuration). Files
written by container processes appear in `~/.aws`, `~/.config`,
and sibling source repos on the host. The container is not a
sandbox for protecting host secrets.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whether the mounts are in the user's home directory depends on whether the repo with the devcontainer was cloned into the home directory or not. We do not explicitly write to $HOME/.aws on the host, but that will be the path if the repo with the devcontainer is a sibling of $HOME/.aws.

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

Labels

improvement Improves an existing functionality non-breaking Introduces a non-breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants