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.

Description of problem:
Client applications are not able to establish ssl23 connection once isclib initialized.

Version-Release number of selected component (if applicable):
bind-libs-lite-9.9.4-73.el7.x86_64

How reproducible:
100%

Additional info:
See https://bugzilla.redhat.com/show_bug.cgi?id=1613174#c10 for detailed description

This seems to be variant of bug #1668682 for RHEL7. It still resets default random generator from OpenSSL with custom generator based on SHA1 from BIND. Because it should be rebased to the same version, the same solution should be used if possible.

It is initialized from lib/dns/openssl_link.c, dst__openssl_init(). If ENGINE_get_default_RAND() does return non-NULL value, it should not replace it. It might be possible to workaround this from DHCP, if it did call ENGINE_set_default_RAND(). There is no way to set it by current BIND library API on library initialization. 

dst_lib_init2 could be used to pass engine name from dns_lib_init(), currently it is always NULL.

*** This bug has been marked as a duplicate of bug 1685940 ***