Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
Crypto-policy non-compliance is reported by rpmlint.
Since RHEL-8.0 we have system-wide crypto policies - usage of cryptographic protocols such as TLS that are enforced system-wide. In general we want all applications in RHEL to be compliant with the crypto policy set on the system (see policy [1] inherited from Fedora).
Rpmlint detected that galera uses SSL_CTX_set_cipher_list from OpenSSL library without PROFILE=SYSTEM. This indicates that a custom setting is used rather than system-wide crypto-policies setting. It is not a problem as long as it is intentional (e.g. specific algorithm is requested by user or configuration). However, unintentional usage might be a potential bug.
Could you please inspect relevant parts of the code, check that this is not rpmlint false positive and verify that custom setting is used intentionally?
* If yes, feel free to close this BZ as NOT-A-BUG.
* If not, could you please consider using system-wide crypto policy setting (PROFILE=SYSTEM) instead of custom setting?
[1] https://docs.fedoraproject.org/en-US/packaging-guidelines/CryptoPolicies
Version-Release number of selected component (if applicable):
galera-25.3.26-1.module+el8.1.0+3974+90eded84
How reproducible:
100%
Steps to Reproduce:
1. rpmlint galera-25.3.26-1.module+el8.1.0+3974+90eded84.x86_64.rpm
Expected results:
No crypto-policy-non-compliance warning.
Actual results:
galera.x86_64: W: crypto-policy-non-compliance-openssl /usr/lib64/galera/libgalera_smm.so SSL_CTX_set_cipher_list
galera.x86_64: W: crypto-policy-non-compliance-openssl /usr/sbin/garbd SSL_CTX_set_cipher_list
It is used intentionally.
As far as I understand, it is used to enable OpenSSL ECDH functionality AND to apply user configuration.
I'd like someone else to double check after me, though.
Affected file: "galerautils/src/gu_asio.cpp"