Windows CLI v2.122.0 blocked by Smart App Control
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Start by reading the Windows release packaging and signing configuration, then check how the v2.122.0 release binary was produced. Reproduce the Smart App Control block on a supported Windows environment and compare its signing and reputation details with Microsoft’s guidance. Done means identifying a supported resolution that lets the official CLI run with Smart App Control and TLS verification enabled.
由索引模型根据 Issue 内容生成。
描述
Affected area
Installation
Supabase CLI version
v2.122.0 (official downloaded release; execution blocked before --version can run)
Operating system
Windows with Smart App Control enforced; exact OS build not included in the available diagnostic summary
Installation method
GitHub release binary
Command
Attempted execution of the official Windows supabase.exe. The exact original invocation is not available in the saved diagnostic summary; Windows blocks the executable from starting.
Actual output
Reported diagnostic identifiers:
Error: 4551
Code Integrity event: 3077
Enforcement policy: VerifiedAndReputableDesktop
The official Windows download passed checksum verification but could not execute. These are the recorded identifiers, not a verbatim full Event Viewer log.
Expected behavior
The official CLI should run while Smart App Control remains enabled. Is a signed Windows build or another supported resolution available that preserves this protection?
Steps to reproduce
- Download the official Windows Supabase CLI v2.122.0 release.
- Verify its checksum (passed in the affected environment).
- Attempt to execute it with Smart App Control enforced.
- Observe error 4551 and Code Integrity event 3077 under policy VerifiedAndReputableDesktop.
No security bypass was attempted. I cannot confirm whether this occurs on every Smart App Control-enabled machine.
Crash report ID
No response
Docker and service versions
Additional context
Microsoft documents the policy in its Smart App Control testing guidance: https://learn.microsoft.com/en-us/windows/apps/develop/smart-app-control/test-your-app-with-smart-app-control
TLS verification is also unresolved in this environment, but its cause has not been established. This report does not attribute that separate issue to the CLI or to Smart App Control.
Please advise on a supported resolution that keeps Windows protection and TLS verification intact.
- 主要语言
- TypeScript
- 星标
- 2.4k
- 派生
- 537
- 平均合并
- 17 小时 22 分钟
- 30 天内合并 PR
- 391
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
supabase/cli 的其他 Issue
-
db schema declarative sync: no way to fail (non-zero exit) when the generated migration is destructive可能重新可做 关联的 PR 已关闭且未合并。 未关闭✨ Feature supabase/cli
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
stack: every Edge Function request starts a new worker, so the same function never reuses one and each call pays a cold start可能已有人在做 @7ttp 于 3 天前认领。 未关闭🐛 Bug supabase/cli
难度 3/5 1-2 天 新手友好度 58/100
维护者通常 1 天内回复
-
🐛 Bug supabase/cli
难度 4/5 3-5 天 新手友好度 48/100
维护者通常 1 天内回复
-
Explicit local function bundling falls back to API bundling when Docker is unavailable可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭🐛 Bug open-for-contribution supabase/cli
难度 3/5 1-2 天 新手友好度 68/100
维护者通常 1 天内回复
-
🐛 Bug supabase/cli
难度 4/5 3-5 天 新手友好度 54/100
supabase/cli#7200 · 1 条评论 · 1 个 reaction · 已指派 1 人 ·
维护者通常 1 天内回复
相似的 Issue
-
area:cli bug P4
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
bug from-studio
难度 2/5 1-3 小时 新手友好度 65/100
esengine/DeepSeek-Reasonix#14868 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
linxiv-dev/linXiv#384 · 1 条评论 ·
维护者通常 1 天内回复
-
scope:core type:security
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
mailgun/mailgun.js#544 ·