On Fedora 43, Unbound (unbound-1.24.x) fails to start when running under FIPS crypto policy because QUIC/DoQ crypto initialization (ngtcp2_crypto_ossl_init()) fails. This prevents FreeIPA installation from completing, as FreeIPA attempts to restart Unbound during DNS-over-TLS (DoT) configuration. Unbound initializes the QUIC (DoQ) backend even when DoQ is not enabled in the configuration. Under FIPS or DEFAULT-FIPS crypto policy, the ChaCha20-Poly1305 cipher is disallowed, causing ngtcp2_crypto_ossl_init() to fail and Unbound to abort. This issue does not occur in Fedora 42 (Unbound 1.22.x) where QUIC support was not integrated. Reproducible: Always Steps to Reproduce: Use Fedora 43 with FIPS or DEFAULT-FIPS system crypto policy. 1. Install Unbound 1.24.x. 2.Start or restart Unbound: systemctl restart unbound OR run FreeIPA installation with DoT which triggers: systemctl restart unbound.service Observe service failure. Actual Results: Unbound crashes during startup: error: ngtcp2_crypto_ossl_init failed fatal error: could not create doq_table: out of memory unbound.service: Main process exited, status=1/FAILURE Expected Results: Unbound should start successfully under FIPS crypto policy. QUIC/DoQ crypto (ngtcp2) should not be initialized unless DoQ is explicitly enabled in the configuration. A crypto policy failure should not abort the service when QUIC is unused.
Created proposal at: https://github.com/NLnetLabs/unbound/pull/1381 This does not seem to be reproducible by just setting FIPS policy. It seems enforcement by kernel fips=1 parameter should happen.
FEDORA-2025-742ec282bf (unbound-1.24.1-5.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2025-742ec282bf
FEDORA-2025-f5f66984a9 (unbound-1.24.1-5.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-f5f66984a9
FEDORA-2025-742ec282bf (unbound-1.24.1-5.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
In addition, this problem is fixed also in new ngtcp2 version. That does not fail anymore on crypto failures. Bug #2404703.
FEDORA-2025-f5f66984a9 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-f5f66984a9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-f5f66984a9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-90281e4554 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-90281e4554` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-90281e4554 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-90281e4554 (unbound-1.24.2-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.