仓库里硬编码的公钥 gc-2026-11 没有对应的私钥(.signing/ 在 .gitignore 里, 私钥从来没入过库,也无法找回),导致 build.sh 每次签名都失败,version.json 始终是「未签名」。而客户端默认 RequireSignedManifest=true,未签名清单一律 拒绝更新 —— 自动更新实际上完全不可用。 改动: - keygen 生成新密钥 gc-2026-12(指纹 ee6083be47a87907),公钥写进 SignatureKeyring;旧 gc-2026-11 保留一个版本周期,标注为「私钥遗失、已停用」 - GC-SAVEDOG 的 DefaultKeyId 与 build_funcs.sh 的 GC_SIGNING_KEY_ID 默认值 同步改为 gc-2026-12,避免 keyId 与私钥不匹配又签出 Invalid - GC.Tests 构造可信清单时用的 keyId 改为 gc-2026-12(原来硬编码旧 keyId, 换钥匙后会判成 Invalid) - README 补上密钥轮换的实际步骤与「换钥匙老客户端就更新不了」的代价 - Directory.Build.props 版本 1.0.7 → 1.0.9(此前只靠 -version 传参, 仓库里一直停在 1.0.7,与实际发布脱节) - version.json / model/version.json 换成 1.0.9 且带 gc-2026-12 签名, 两份字节一致 验证: - GC.Tests --update-test 全通过,日志里是「清单验签通过(gc-2026-12)」, 篡改清单被判 Invalid 并拒绝更新 - GC-SAVEDOG verify --manifest version.json → Verified - 三平台重新出包:win-amd64 109 MB、win-arm64 105 MB、mac-arm64 57 MB 注意:1.0.8 及更早的客户端只认识旧公钥,这份清单在它们眼里是「签名无效」, 与之前的「未签名」等价 —— 都不会自动更新。要让自动更新真正生效,需要把 带新公钥的 1.0.9 发出去。
38 lines
1.1 KiB
JSON
38 lines
1.1 KiB
JSON
{
|
|
"schemaVersion": 1,
|
|
"id": "scale-calculator",
|
|
"name": "Scale Calculator",
|
|
"nameI18n": {
|
|
"zh-CN": "比例尺计算器",
|
|
"en": "Scale Calculator"
|
|
},
|
|
"author": "Morris GC",
|
|
"description": "把比例尺变成可以拖、可以量的可视化标尺",
|
|
"descriptionI18n": {
|
|
"zh-CN": "三种求解模式、图上/实地双条对比、线段式比例尺自动换挡、比例尺光谱、真实地标实地尺与练习闯关。",
|
|
"en": "Three solve modes, dual map/real bars, auto-ranging graphic scale, scale spectrum, real-world landmarks and practice quizzes."
|
|
},
|
|
"tags": [
|
|
"geography",
|
|
"map",
|
|
"scale",
|
|
"calculator"
|
|
],
|
|
"entry": "scales.json",
|
|
"license": "MIT",
|
|
"assembly": "ScaleCalculatorModel.dll",
|
|
"type": "GC.ScaleCalculator.ScaleCalculatorFactory",
|
|
"preview": "preview.png",
|
|
"apiVersion": 1,
|
|
"version": "1.6",
|
|
"chrome": {
|
|
"titleBar": "#FFFFFF",
|
|
"titleBorder": "#E3E8F3",
|
|
"titleText": "#111A2E",
|
|
"button": "#5B6A86",
|
|
"frame": "#F4F6FB"
|
|
},
|
|
"build": "105653737d",
|
|
"updatedAt": "2026-11-18T10:16:41Z"
|
|
}
|