Launcher test suite: trusted build identity for executables it runs, and run the suite in CI
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
研究方向
Read the launcher test suite and run_launcher_tests.py, then trace how testing builds are identified and how CI builds and runs the launcher tests. The issue names the guarded launch paths and integration checks to cover, but the trusted identity mechanism and CI changes span multiple components. Done means changed or mixed executables are refused on every guarded path and the default stand-in payload suite cases run in CI with failures failing the job.
由索引模型根據 Issue 內容生成。
描述
The launcher test suite only runs programs it can identify as testing builds, and it refuses non-testing programs before they start (PR #253). Two hardening steps were deliberately left out of 0.6.5 and are tracked here.
1. Trusted build identity for executables the suite runs
Today a program counts as a testing build when it carries the testing-only named resource, the testing hook strings inside its sections, and a matching PE checksum. That rejects release builds, modified copies and the runnable canaries. It is not a provenance proof: the PE checksum is unkeyed, so a binary crafted on purpose could carry the same resource, strings and a recomputed checksum.
Proposal: have the testing build write an identity the suite can verify independently of the file itself, such as a build manifest with the full SHA-256 of each executable produced in that build (launcher, restorer, uninstaller, canaries), checked before every launch, or a keyed marker. Mixed or changed images should fail. Add a negative control with a runnable canary that carries the resource, the strings and a valid recomputed checksum, and show that it is refused on every guarded launch path.
2. Run the launcher suite in CI
CI builds the testing launcher and runs the core tests, but it does not run run_launcher_tests.py. The suite's integration checks can regress while CI stays green: the runnable-canary refusals on each entry point, the inherited-override stripping, the helper-permission negative control, and the edition/junction temp-folder checks.
Proposal: run the default launcher-suite cases on the stand-in payload in CI, including both launcher entry points (--launcher and --no-direct-launcher) and the helper and temp integration checks, with failures failing the job.
- 主要語言
- C++
- 星號
- 12
- 分支
- 2
- 平均合併
- 3 小時 10 分鐘
- 30 天內合併 PR
- 171
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
phantoslayer21/wronggpu 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 88/100
phantoslayer21/wronggpu#275 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 82/100
phantoslayer21/wronggpu#274 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 88/100
phantoslayer21/wronggpu#241 ·
維護者通常 1 天內回覆
-
bug build
難度 2/5 1-3 小時 新手友好度 74/100
phantoslayer21/wronggpu#234 ·
維護者通常 1 天內回覆
-
bug build
難度 2/5 1-3 小時 新手友好度 80/100
phantoslayer21/wronggpu#233 ·
維護者通常 1 天內回覆
查看 phantoslayer21/wronggpu 的全部 Issue
相似的 Issue
-
ai_p2
難度 2/5 1-3 小時 新手友好度 80/100
ClickHouse/ClickHouse#132519 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
juce-framework/JUCE#1810 ·
-
難度 1/5 1 小時以內 新手友好度 82/100
petercorke/robotics-toolbox-python#952 ·
維護者通常 1 天內回覆
-
NatronRenderer: a Python error in the script (-t / project script) doesn't change the exit status未關閉func:engine type:bug
難度 2/5 1-3 小時 新手友好度 72/100
NatronGitHub/Natron#1276 ·
維護者通常 1 天內回覆
-
難度 1/5 1-3 小時 新手友好度 77/100
維護者通常 1 天內回覆