Debian install fails on Bookworm in FIPS mode

未關閉
#595 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
35/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
debian, linux
領域
devops

研究方向

Start with the Debian repository metadata generation and publishing entry points in this packaging repository; the issue does not name specific files or tests. Reproduce the reported apt-get update failure on Debian Bookworm with FIPS mode enabled, then check whether removing MD5 hashes from the Bookworm InRelease metadata resolves it. Done means the documented apt installation flow succeeds in that environment without breaking repository metadata verification.

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

描述

On Debian Bookworm with FIPS mode enabled, when following the official instructions for installing from the apt repository, the second invocation of apt-get update fails with

+ apt-get update
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm-updates InRelease
Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease
Get:4 https://download.docker.com/linux/debian bookworm InRelease [43.3 kB]
Get:5 https://download.docker.com/linux/debian bookworm/stable amd64 Packages [31.3 kB]
Fetched 74.6 kB in 1s (87.5 kB/s)
Reading package lists...fatal error in libgcrypt, file ../../src/misc.c, line 92, function _gcry_fatal_error: requested algo not in md context

Fatal error: requested algo not in md context
bash: line 6:   274 Aborted                 apt-get update

This is tracked (and probably won't be fixed) as bug 1014517 in the Debian issue tracker. It only happens on Bookworm because the version of libgcrypt in that release removed an exception that allowed MD5 in FIPS mode.

FIPS mode is a Linux kernel mode that disallows certain cryptographic algorithms. Whether it is active in the kernel is controlled by, and exposed at, /proc/sys/crypto/fips_enabled.

I believe that one way to work around this would be to remove the MD5 hashes from the InRelease file for Bookworm. I noticed that none of the distribution's default InRelease files contain them anymore, despite the lingering recommendation to include them. I'd venture to say that the number of Bookworm users that actually rely on MD5 hashes for package installation is extremely small. On the other hand, I believe that those users who are forced to enable FIPS mode, because, say a compliance framework requires them to, are also eager to upgrade to Bookworm (stable) simply because it has fewer reported vulnerabilities (CVEs), which many compliance frameworks require them to address promptly.

主要語言
Dockerfile
星號
37
分支
42
平均合併
16 小時 53 分鐘
30 天內合併 PR
30

環境準備

  • 提供 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

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

docker/packaging 的其他 Issue

查看 docker/packaging 的全部 Issue

相似的 Issue

更多 DevOps Issue

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

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