smoketest for browser vuln, rough draft of Windows security doc #6822
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
https://github.com/openai/codex/blob/8542bfd65309a65ea194fe20d41b9058bfad03de/windows-sandbox-rs/sandbox_smoketests.py#L441-L458
By replacing the old .SsH case-variation smoke test with the new Start-Process check we no longer exercise whether .ssh remains protected against case tricks. The allowlist logic is scoped per path, so the existing .GiT case test does not tell us anything about .ssh: if the sandbox still mishandles .SsH (which was the whole reason for the prior test), that regression will now go unnoticed. Given that .ssh contains private keys, losing this coverage leaves a high-value escape untracked. Please keep the .ssh variation test in addition to the new browser-launch scenario so we continue to catch that failure.
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
No description provided.