fix(updater): verify the signer identity, not just the seal, on macOS updates

已關閉
#1,588 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
43/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
dart, flutter, macos
領域
desktop, security

研究方向

Start by reading MacosSparkleInstaller._verifyCodesign and trace how the running app and downloaded bundle are identified during macOS updates. Compare the available codesign or spctl checks with the unsigned-install fallback described in the issue. Done means updates accept the same signer identity and reject a differently signed bundle, with a documented check for ad-hoc installs.

由索引模型根據 Issue 內容生成。

描述

bug P2 security

Problem

MacosSparkleInstaller._verifyCodesign runs codesign --verify --deep --strict on the downloaded bundle. That proves the seal is intact, not who signed it: any validly signed (even ad-hoc) bundle in the zip passes and replaces the installed app.

Expected

Require the new bundle to be signed by the same identity as the running app (compare Team ID / designated requirement via codesign -dv / codesign -R, or spctl --assess --type execute), and refuse otherwise. For unsigned (ad-hoc) installs, fall back to a documented check such as the release checksum.

Notes

The zip comes from GitHub over HTTPS, so exposure needs a compromised release, but this is the check meant to defend against it.

主要語言
Dart
星號
23
分支
1
平均合併
49 分鐘
30 天內合併 PR
496

環境準備

在 Codespaces 中開啟

在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

QueryaHub/Querya-Desktop 的其他 Issue

查看 QueryaHub/Querya-Desktop 的全部 Issue

相似的 Issue

更多 Dart Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。