Debian install fails on Bookworm in FIPS mode

オープン
#595 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
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分
マージ済み PR(30日)
30

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

docker/packaging のほかの issue

docker/packaging の issue をすべて見る

似ている issue

DevOps の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。