dirmngr: add standalone spec to restore HTTPS keyserver support#17704
Draft
mfrw wants to merge 1 commit into
Draft
dirmngr: add standalone spec to restore HTTPS keyserver support#17704mfrw wants to merge 1 commit into
mfrw wants to merge 1 commit into
Conversation
gnupg2 in Azure Linux 3.0 ships without the dirmngr daemon because gpg's
configure script silently drops it when no TLS backend (gnutls or ntbtls)
is available, and gnutls cannot be added to the gnupg2 BuildRequires
without dragging gnutls + nettle + gmp + p11-kit + libtasn1 + libffi +
libidn2 + libunistring + autogen-libopts + gc into the bootstrap
toolchain (see toolkit/scripts/toolchain/build_official_toolchain_rpms.sh
where gnupg2 is part of the readline -> npth -> libassuan -> libksba ->
gnupg2 -> gpgme -> tdnf chain).
This breaks every workflow that relies on `gpg --keyserver ...
--recv-keys` over HKPS, including the upstream golang Docker image
build.
Add a new SPECS/dirmngr/dirmngr.spec that reuses the gnupg-%{version}
source tarball but is built out-of-toolchain with gnutls-devel,
curl-devel and openldap-devel, and ships only the dirmngr binary, the
dirmngr-client utility, the dirmngr_ldap LDAP helper and their man
pages. Everything else from the same tarball remains owned by gnupg2.
Entangle Version and Release with gnupg2 in
toolkit/scripts/check_entangled_specs.py so future gnupg2 CVE rebuilds
automatically force a matching dirmngr rebuild and there is no risk of
drift between the two packages.
Fixes ADO 62225284
Refs #3142
Signed-off-by: Muhammad Falak R Wani <falakreyaz@gmail.com>
mfrw
commented
Jun 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
gnupg2 in Azure Linux 3.0 ships without the dirmngr daemon because gpg's
configure script silently drops it when no TLS backend (gnutls or ntbtls)
is available, and gnutls cannot be added to the gnupg2 BuildRequires
without dragging gnutls + nettle + gmp + p11-kit + libtasn1 + libffi +
libidn2 + libunistring + autogen-libopts + gc into the bootstrap
toolchain (see toolkit/scripts/toolchain/build_official_toolchain_rpms.sh
where gnupg2 is part of the readline -> npth -> libassuan -> libksba ->
gnupg2 -> gpgme -> tdnf chain).
This breaks every workflow that relies on
gpg --keyserver ... --recv-keysover HKPS, including the upstream golang Docker imagebuild.
Add a new SPECS/dirmngr/dirmngr.spec that reuses the gnupg-%{version}
source tarball but is built out-of-toolchain with gnutls-devel,
curl-devel and openldap-devel, and ships only the dirmngr binary, the
dirmngr-client utility, the dirmngr_ldap LDAP helper and their man
pages. Everything else from the same tarball remains owned by gnupg2.
Entangle Version and Release with gnupg2 in
toolkit/scripts/check_entangled_specs.py so future gnupg2 CVE rebuilds
automatically force a matching dirmngr rebuild and there is no risk of
drift between the two packages.
Fixes ADO 62225284
Refs #3142
Signed-off-by: Muhammad Falak R Wani falakreyaz@gmail.com