RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2027735 - [RFE] Rebase unbound to latest stable release
Summary: [RFE] Rebase unbound to latest stable release
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: unbound
Version: 8.6
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Petr Menšík
QA Contact: Petr Sklenar
Šárka Jana
Depends On:
Blocks: 2071968 2081958 2116730 2116737
TreeView+ depends on / blocked
Reported: 2021-11-30 14:28 UTC by Florencia Fotorello
Modified: 2022-11-08 10:52 UTC (History)
6 users (show)

Fixed In Version: unbound-1.16.2-2.el8
Doc Type: Enhancement
Doc Text:
.`unbound` rebased to version 1.16.2 The `unbound` component has been updated to version 1.16.2. `unbound` is a validating, recursive, and caching DNS resolver. Notable improvements include: * With the ZONEMD Zone Verification with `RFC 8976` support, recipients can now verify the zone contents for data integrity and origin authenticity. * With `unbound`, you can now configure persistent TCP connections. * The SVCB and HTTPS types and handling according to the Service binding and parameter specification via the DNS `draft-ietf-dnsop-svcb-https` document were added. * `unbound` takes the default TLS ciphers from crypto policies. * You can use a Special-Use Domain `home.arpa.` according to the `RFC8375`. This domain is designated for non-unique use in residential home networks. * `unbound` now supports selective enabling of `tcp-upstream` queries for stub or forward zones. * The default of `aggressive-nsec` option is now `yes`. * The `ratelimit` logic was updated. * You can use a new `rpz-signal-nxdomain-ra` option for unsetting the `RA` flag when a query is blocked by an Unbound response policy zone (RPZ) nxdomain reply. * With the basic support for Extended DNS Errors (EDE) according to the `RFC8914`, you can benefit from additional error information.
Clone Of:
Last Closed: 2022-11-08 09:51:08 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-104342 0 None None None 2021-11-30 14:36:48 UTC
Red Hat Product Errata RHSA-2022:7622 0 None None None 2022-11-08 09:51:26 UTC

Comment 10 Petr Menšík 2022-05-06 15:50:41 UTC
I may have found relative simple way to retain ABI compatibility, but using recent unbound code. It is not yet properly tested, but candidate change on upstream main branch is pushed to github:


Comment 11 Petr Menšík 2022-05-06 17:11:23 UTC
Prepared copr build for epel8 on COPR [1]. Infrastructure is broken, so I am unsure it works as it should. But basic things seems to be working.
The change on top of released version 1.5.0 is in own branch [2]

1. https://copr.fedorainfracloud.org/coprs/pemensik/unbound/
2. https://github.com/InfrastructureServices/unbound/tree/rhel8-no-abi-break-1.15

Comment 12 Petr Menšík 2022-05-06 17:42:41 UTC
The change looks good, even previously compiled unbound-host is able to continue with a new library and works.

But at least libreswan would require a change too, because it expects changed callback format. But that checks only version and our version would not compile libreswan.

Fail at:

cc -DTimeZoneOffset=timezone -pthread -std=gnu99 -g -Werror -Wno-missing-field-initializers -Wno-lto-type-mismatch -Wno-maybe-uninitialized -Wall -Wextra -Wformat -Wformat-nonliteral -Wformat-security -Wundef -Wmissing-declarations -Wredundant-decls -Wnested-externs -O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -fstack-protector-all -fno-strict-aliasing -fPIE -DPIE -DNSS_IPSEC_PROFILE -DXFRM_LIFETIME_DEFAULT=30 -DUSE_IKEv1 -DKERNEL_XFRM -DUSE_XFRM_INTERFACE -DUSE_DNSSEC -DDEFAULT_DNSSEC_ROOTKEY_FILE=\""/var/lib/unbound/root.key"\" -DHAVE_LABELED_IPSEC -DHAVE_SECCOMP -DLIBCURL -DUSE_LINUX_AUDIT -DUSE_SYSTEMD_WATCHDOG -DLIBLDAP -DHAVE_NM -DUSE_PAM_AUTH -DUSE_3DES -DUSE_AES -DUSE_CAMELLIA -DUSE_CHACHA -DUSE_DH31 -DUSE_MD5 -DUSE_SHA1 -DUSE_SHA2 -DUSE_PRF_AES_XCBC -DUSE_NSS_KDF -DDEFAULT_RUNDIR=\"/run/pluto\" -DIPSEC_CONF=\"/etc/ipsec.conf\" -DIPSEC_CONFDDIR=\"/etc/ipsec.d\" -DIPSEC_NSSDIR=\"/var/lib/ipsec/nss\" -DIPSEC_CONFDIR=\"/etc\" -DIPSEC_EXECDIR=\"/usr/libexec/ipsec\" -DIPSEC_SBINDIR=\"/usr/sbin\" -DIPSEC_VARDIR=\"/var\" -DPOLICYGROUPSDIR=\"/etc/ipsec.d/policies\" -DIPSEC_SECRETS_FILE=\"/etc/ipsec.secrets\" -DFORCE_PR_ASSERT -DUSE_FORK=1 -DUSE_VFORK=0 -DUSE_DAEMON=0 -DUSE_PTHREAD_SETSCHEDPRIO=1 -DGCC_LINT -DHAVE_LIBCAP_NG \
	-I. -I../../OBJ.linux.x86_64.f339a8b5d56c49dda351b3e4a108cf33/programs/pluto -I../../include -I/usr/include/nss3 -I/usr/include/nspr4  -I/builddir/build/BUILD/libreswan-4.6/programs/pluto/linux-copy \
	-DHERE_FILENAME=\"programs/pluto/ikev1.c\" \
	-MF ../../OBJ.linux.x86_64.f339a8b5d56c49dda351b3e4a108cf33/programs/pluto/ikev1.d \
	-MP -MMD -MT ikev1.o \
	-o ../../OBJ.linux.x86_64.f339a8b5d56c49dda351b3e4a108cf33/programs/pluto/ikev1.o \
	-c /builddir/build/BUILD/libreswan-4.6/programs/pluto/ikev1.c
/builddir/build/BUILD/libreswan-4.6/programs/pluto/ikev2_ipseckey_dnsr.c: In function 'dns_qry_start':
/builddir/build/BUILD/libreswan-4.6/programs/pluto/ikev2_ipseckey_dnsr.c:471:27: error: passing argument 6 of 'ub_resolve_event' from incompatible pointer type [-Werror=incompatible-pointer-types]
       dnsr->qclass, dnsr, ipseckey_ub_cb, &dnsr->ub_async_id);
In file included from /builddir/build/BUILD/libreswan-4.6/programs/pluto/ikev2_ipseckey_dnsr.c:31:
/usr/include/unbound-event.h:258:52: note: expected 'ub_event_callback_type' {aka 'void (*)(void *, int,  void *, int,  int,  char *)'} but argument is of type 'void (*)(void *, int,  void *, int,  int,  char *, int)'
  int rrclass, void* mydata, ub_event_callback_type callback,

Comment 13 Petr Menšík 2022-05-09 13:49:52 UTC
Breaking of libreswan can be avoided by faking 1.7.x version in unbound-event.h.  That should also fix any other potential issues with compilation time detection. ub_version() would still report correct version of unbound. But version taken from header would report 1.7.1150 for 1.15.0 release.

Comment 15 Petr Menšík 2022-05-09 15:42:00 UTC
Thread about this at unbound-users mailing list:

I am not proposing this change to normal unbound, therefore it would be downstream only change. No Merge request would be created at upstream. Not included in RHEL9+ or Fedora. Should would also for RHEL7, but no production build would be done for it.

It seems most of software uses just ub_resolve_async, which should be unaffected by this change.

Comment 26 errata-xmlrpc 2022-11-08 09:51:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: unbound security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.