rpi-fw-crypto: can the dependency on GnuTLS be optional instead?

未关闭
#222 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
c
领域
embedded-iot

调研方向

Read the rpi-fw-crypto implementation, especially the sign command's hash_file() and the hmac command used by the initramfs; the issue names no source files or tests. Check how the binary links to GnuTLS and whether that dependency can be made optional for hmac. Done means hmac works without GnuTLS while sign retains its required hashing behavior.

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

描述

Hi,

The initramfs that rpi-image-gen builds with the rpi-idp-luks2 layer runs rpi-fw-crypto hmac to unlock LUKS2. Because rpi-fw-crypto links against GnuTLS, the initramfs also has to carry GnuTLS and its dependencies: 2.28 MB at zstd -19, close to 25% of my small initramfs test. GnuTLS is only used by sign (in hash_file()), but the binary won’t load without it, even for hmac.

I saw that #203 was closed because GnuTLS is used elsewhere in RPi OS. In my initramfs, though, rpi-fw-crypto appears to be its only user, in this particular configuration I am testing.

The use case I’m considering is reducing churn in the generated boot.img, which affects OTA transfer size where those matters. I suppose the counterargument is that I could simply pin the package versions instead of always pulling the latest via apt.

主要语言
C
星标
351
派生
103
平均合并
1 天 18 分钟
30 天内合并 PR
4

环境准备

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

从这里开始

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

raspberrypi/utils 的其他 Issue

查看 raspberrypi/utils 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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