Skip to content

security-local: name every launch-flagged PTY write the OSC 367 audit reads - #1129

Merged
nedtwigg merged 1 commit into
mainfrom
fix/security-local-launch-writes
Oct 16, 2026
Merged

nedtwigg merged 1 commit into
mainfrom
fix/security-local-launch-writes

Conversation

@dormouse-bot

Copy link
Copy Markdown
Collaborator

The OSC 367 FAIL IF in docs/specs/security-local.md → "Terminal output" tells the auditor which writes may carry launch, but its list was wrong in two ways: it placed typeToolCommand in lib/src/lib/terminal-lifecycle.ts (it lives in use-dor-control.ts), and it left out the helper terminal's autorun write in watchHelper. An auditor following the rule would look for the first in the wrong file and never be pointed at the third.

The edit names all three writePty(..., { launch: true }) call sites in lib/src (grep -rn "launch: true" lib/src, non-test) with their actual paths. Docs-only, so no test; spec-lint passes and the word count is within budget.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying mouseterm with  Cloudflare Pages  Cloudflare Pages

Latest commit: 2e7bf5c
Status: ✅  Deploy successful!
Preview URL: https://d2f970c3.mouseterm.pages.dev
Branch Preview URL: https://fix-security-local-launch-wr.mouseterm.pages.dev

View logs

@nedtwigg
nedtwigg merged commit f1b7cc7 into main Oct 16, 2026
12 checks passed
@nedtwigg
nedtwigg deleted the fix/security-local-launch-writes branch October 16, 2026 19:52

This branch was successfully deployed

No deployments
hosted-preview — 2e7bf5cd Deployed Oct 16, 2026 by nedtwigg via cleanup #1384
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.

2 participants