replay-regression

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Independently replay a PoC

独立重放 PoC

When to Use

使用场景

Input: candidate, frozen source records, complete sealed reproduction package and registry assignment. Use a fresh context distinct from the reproducer. Follow project guidance before target work.
输入:候选项、冻结的源记录、完整且已封存的复现包以及注册表分配项。使用与复现者不同的全新上下文。 开始目标操作前,遵循项目指导。

When NOT to Use

不适用场景

Authoring or repairing the PoC. Return changes to the caller for reproduction; changed PoCs require new reproduction and replay.
编写或修复 PoC。将更改退回给调用方进行复现;经更改的 PoC 需要重新复现和重新重放。

Replay

重放

  1. Read the standard and file contract. Verify the package; read setup and security guidance. Stop execution if prerequisites fail.
  2. Independently build and run actual S0/S1 only inside your attempt directory; never reuse another attempt's build output. List every build directory in
    build_dirs
    . Execute the unchanged PoC with the same input against both. Record whether S0 behaves correctly and S1 exhibits the claimed failure.
  3. Check real interface reachability using only the claimed user's/attacker's access. Save setup, versions, commands, observations and separate logs.
  4. Write and seal
    replay.json
    , referencing the reproduction record and original PoC/input. Record divergence or blockers; uncertainty stays unresolved. Release temporary resources without deleting evidence.
  1. 读取标准和文件契约。验证复现包;阅读设置与安全指南。如果前置条件不满足,停止执行。
  2. 仅在你的尝试目录内独立构建并运行实际的 S0/S1;绝不复用其他尝试的构建产物。在
    build_dirs
    中列出每一个构建目录。使用相同输入对两者执行未经更改的 PoC。记录 S0 是否行为正确,以及 S1 是否出现所声称的故障。
  3. 仅使用所声明用户/攻击者的访问权限,检查真实接口的可达性。保存设置、版本、命令、观察结果和单独的日志。
  4. 编写并封存
    replay.json
    ,引用复现记录以及原始 PoC/输入。记录差异或阻塞项;不确定事项保持未解决状态。释放临时资源,但不得删除证据。

Report Back

回报结果

Keep detailed evidence in the sealed package. Return only:
  • Status:
    complete
    or
    blocked
    , matching the record.
  • Record: sealed
    replay.json
    path, or why none was produced.
  • Result: one sentence describing observed agreement or divergence.
  • Blocker: missing prerequisite or required caller action, if blocked.
Completion means the replay attempt finished, not that the regression is confirmed.
将详细证据保留在已封存的包中。仅返回:
  • 状态:
    complete
    或
    blocked
    ,与记录一致。
  • 记录:已封存的
    replay.json
    路径,或未生成记录的原因。
  • 结果:用一句话描述观察到的一致或差异。
  • 阻塞项:缺失的前置条件或调用方需要采取的操作(如有阻塞)。
完成意味着重放尝试已结束,并不表示回归问题已得到确认。

Rationalizations to Reject

需要拒绝的理由

  • “The previous logs look right”: replay requires your own execution.
  • “之前的日志看起来没问题”:重放要求你自己执行验证。