Repository navigation
Ommega 2.3.0
本版安装包缺少 ommega-rkp,安装后「设置 -> 自动化」不可用;请使用 2.3.1。
本版安装包缺少 ommega-rkp,安装后「设置 -> 自动化」不可用;请使用 2.3.1。
dice_chain_hex / signing / device / issuance)。内容以 AES-256-GCM 加密保存于 data/rkp/seed.enc,密钥是每台设备随机生成的 data/rkp/master.key(均 0600);从其它设备拷回的密文会显示「无法解密」,而不是等到签发时才 失败。模块不内置任何种子或证书。 - 移植 Duck ToolBox 的 RKP 引擎(MIT,a-side/source/rkp-engine):每次签发取新 challenge、 生成新的 P-256 证明密钥、用导入的叶身份签 CSR v3,校验返回链后导出 keybox。签发结果与手工导入 走同一套槽位校验,链的级别与 O= 必须和所选槽位一致。 - 新增 ommega-rkp 工具:status / due / seed-import / seed-remove / keybox-import / policy / issue / auto-run。签发前会按目标槽位自动改写材料包里的 security_level,避免用为 TEE 捕获的材料去签 StrongBox。 - 自动续签:按服务器下发的 time_to_refresh_hours 计算临期。keymint 守护进程启动 5 分钟后首次 检查,之后睡到下一个临期时刻(上限 1 天,空闲时每天一次),失败后 6 小时内不重试;与手动 签发共用文件锁,网络与 keybox 写入都在子进程,不会阻塞 TA。 - 应用策略页在本地模式下自动隐藏「认证签名策略」「本地 keygen 时序整形(EWMA)」「CPU 与设备 属性」三张卡片,远程模式照常显示。 - 修复本地模式下顶部刷新总是提示「部分状态无法读取,请重试」。 - 修复 keybox 到期时间解析把 UTCTime 的两位年当成四位年,导致显示成 2611 年。 升级说明:只更新 A 端模块 ZIP 即可,B 端与 Server 无需改动。更新后刷新 WebUI 生效;keymint 由 部署流程重载,无需重启设备。 验证:CI 全绿(A、B、Server、APK、UI)。真机 PJZ110 上验证了 TEE 与 StrongBox 两级签发并安装 到对应槽位(链为 O=TEE / O=StrongBox,各 4 张证书)、引擎 29 项单元测试在设备通过、自动 续签首轮判定「未临期」且未消耗请求。 --- ## 2.3.0 — 2026-11-02 A-side automation page and RKP issuance (A only; B and Server are unchanged, no Server update is required). - Settings → Automation is a full page instead of a sheet. The four keybox download sources are gone: the page imports the user's own CDI material bundle and keybox files, one slot each for TEE and StrongBox, never shared. - The bundle keeps the RKP workbench version 1 contract (dice_chain_hex, signing, device, issuance). It is stored AES-256-GCM encrypted at data/rkp/seed.enc with a per-install key at data/rkp/master.key (both 0600); a blob copied from another device reports as undecryptable instead of failing at issue time. The module ships no seed and no keybox. - The RKP engine is ported from Duck ToolBox (MIT, a-side/source/rkp-engine): each issuance requests a fresh challenge, generates a new P-256 attestation key, signs CSR v3 with the imported leaf identity and exports the verified chain. An issued keybox passes the same slot checks as an imported one: the chain level and O= must match the slot. - New ommega-rkp tool: status, due, seed-import, seed-remove, keybox-import, policy, issue, auto-run. Issuance rewrites security_level in the stored bundle to the target slot, so material captured for TEE cannot be spent on a StrongBox request. - Automatic renewal follows the server-provided time_to_refresh_hours. The keymint daemon checks five minutes after start and then sleeps to the next renewal instant (capped at one day, so one check per day while idle); a failed attempt is not retried for six hours. It shares an flock with the manual path, and the network and keybox work run in a child process, never in the TA. - The per-app policy page hides the authentication-signing, local-keygen EWMA and CPU/device-property cards in local mode; remote mode is unchanged. - Fixed the top refresh reporting "some status could not be read" in local mode. - Fixed keybox expiry parsing treating a two-digit UTCTime year as four digits, which displayed 2611. Upgrade: update the A module ZIP only. B and Server need no change. Refresh the WebUI afterwards; the deploy flow reloads keymint, no reboot needed. Verified: CI green (A, B, Server, APKs, UI). On a PJZ110 device both TEE and StrongBox issuance completed and installed into their slots (chains O=TEE / O=StrongBox, four certificates each), the 29 engine unit tests pass on the device, and the first automatic check reported "not due" without spending a request. Full Changelog: v2.2.2...v2.3.0