RAUC keyring.pem is referenced but never installed into the rootfs

未关闭
  • 哪里不对？
#48 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
rust
领域
release, security

调研方向

Read rauc-system.conf and post-build.sh, especially lines 55–58, to trace how the configured keyring path relates to image contents. Check the image build flow for how release certificates are provided and whether a missing keyring can be detected. Done means the release image includes its provisioned keyring, or the build fails clearly when it is unset.

由索引模型根据 Issue 内容生成。

描述

bug

rauc-system.conf sets [keyring] path=/etc/rauc/keyring.pem, but post-build.sh only leaves a comment and a TODO(release) at lines 55-58 ('drop the real signing cert here') — no keyring.pem is ever installed (no keyring file in the overlay or post-build). RAUC refuses to verify/install any bundle without a keyring, so even once the U-Boot A/B integration lands, rauc install will fail closed until a cert is provisioned. Either bake a per-owner cert at release time or fail the image build loudly if the keyring is unset, rather than shipping an image whose configured keyring path does not exist.

Filed from a repo-wide code audit (working tree at bcad746).

主要语言
Rust
星标
0
派生
0
30 天内没有已合并 PR

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

GoogleBot42/podd 的其他 Issue

查看 GoogleBot42/podd 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。