Debian install fails on Bookworm in FIPS mode

Aperta
#595 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
debian, linux
Ambito
devops

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Dockerfile
Stelle
37
Fork
42
Merge medio
16h 53m
PR unite (30g)
30

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di docker/packaging

Tutte le issue di docker/packaging

Issue simili

Altre issue su DevOps

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.