anomalyco / anomalyco/opencode

Security: fail-closed shell classifier hardening (waves H-L of PR #48638 series)

Open
#49,975 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Context

Part of the fork hardening series proposed in #48638 (branch session-diff-events). Tracker: #49565.

Problem

The shell/command classifier could be steered past the external_directory gate and absorb its own offered grants (fail-open classifications) across many shapes: brace lists, wrappers, absolute paths, redirects, dynamic names, env/eval, ANSI-C escapes, attached options, remote operands, substitutions, variable redirects, and more.

Change set (commit list)
  • 85fd685fc1 tool/permission security
  • 77589d5d1a wave H-A shell
  • 3f69dad8a4 wave I-A shell
  • 4618e51749 wave J-A shell
  • ae98cd2397 wave K shell
  • 7b7e70a6c1 wave L remote/attached
Validation
  • Adversarial base-vs-head proofs for every closed class; official suites green; no new prompts on benign corpora.
  • Intended to land as a standalone stacked PR (see PR #48638 for the integration branch).

Linked: PR #48638 · tracker #49565 · sibling tracking issues listed in a follow-up comment.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with PR #48638 and tracker #49565, then review the listed waves H-L and their shell-classifier changes. Use the adversarial base-vs-head proofs and official suites described in the issue; done means the listed fail-open classes are closed without new prompts on benign corpora.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell, typescript
Domain
cli, security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.