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 1956873 - Stop using nettle directly, switch dnsmasq to openssl
Summary: Stop using nettle directly, switch dnsmasq to openssl
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: dnsmasq
Version: 9.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: beta
: ---
Assignee: Petr Menšík
QA Contact: rhel-cs-infra-services-qe
URL:
Whiteboard:
Depends On:
Blocks: 2067273
TreeView+ depends on / blocked
 
Reported: 2021-05-04 15:05 UTC by Alexander Sosedkin
Modified: 2023-05-04 07:28 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-04 07:28:32 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github themiron/dnsmasq/tree/openssl 0 None None None 2021-06-28 12:14:10 UTC

Comment 1 Petr Menšík 2021-06-28 12:14:12 UTC 
No existing code supports gnutls. But there is existing attempt to support OpenSSL [1] in dnsmasq code, which in my opinion would be more interesting for us. I think it is used on some embedded router devices.

1. https://github.com/themiron/dnsmasq/tree/openssl
Comment 2 Alexander Sosedkin 2021-06-28 12:28:54 UTC 
Switching over to openssl 3.0 sounds fine too.
Comment 3 Petr Menšík 2021-06-29 09:01:36 UTC 
Referenced branch builds under OpenSSL 3.0 successfully. Also unlike nettle support, it passes without errors all ciphers test (used bug #1934936 tool). It seems it works nice even for ghost deactivated in openssl.

I found ecdsa validation [1] uses couple of functions deprecated. Is it possible to EVP_PKEY_* variants instead of EC_KEY_new_by_curve_name, 
o2i_ECPublicKey, ECDSA_do_verify? How important is not using deprecated functions in OpenSSL 3? Is there any example of higher-level API for ECDSA validation?

1. https://github.com/themiron/dnsmasq/blob/989ee9815d795f215d1d12895fbe73d79ac47d41/src/crypto-openssl.c#L310
Comment 4 Petr Menšík 2021-06-29 10:02:44 UTC 
Found some example in man EVP_PKEY_fromdata. Problem with that is they are added only in OpenSSL3. Such concept is not yet present in OpenSSL 1.1. For backward compatibility I think current state would be sufficient.
Comment 5 Petr Menšík 2022-03-23 17:28:55 UTC 
It would solve also GOST algorithm failure. OpenSSL implementation can handle disabled GOST well and passes without a change.
Comment 6 Petr Menšík 2022-03-23 17:35:14 UTC 
It is too late now for inclusion from 9.0. OpenSSL support already exists, even not official. Should be used instead of creation yet another crypto support.
Comment 9 RHEL Program Management 2022-11-04 07:27:47 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Comment 13 RHEL Program Management 2023-05-04 07:28:32 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.