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 2029808 - The libgpg-error is using old inet_addr() unconditionally
Summary: The libgpg-error is using old inet_addr() unconditionally
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libgpg-error
Version: 9.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: 9.0
Assignee: Jakub Jelen
QA Contact: Stanislav Zidek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-07 11:00 UTC by Jakub Jelen
Modified: 2022-05-17 16:32 UTC (History)
0 users

Fixed In Version: libgpg-error-1.42-5.el9
Doc Type: Bug Fix
Doc Text:
Cause: Missing configure check Consequence: Wrong legacy function inet_addr() was used for logging Fix: The configure check was introduced Result: The new modern function inet_pton() is used for logging.
Clone Of:
Environment:
Last Closed: 2022-05-17 16:00:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CRYPTO-5728 0 None None None 2021-12-07 11:14:23 UTC
Red Hat Issue Tracker RHELPLAN-104966 0 None None None 2021-12-07 11:06:52 UTC
Red Hat Product Errata RHBA-2022:4009 0 None None None 2022-05-17 16:00:07 UTC

Description Jakub Jelen 2021-12-07 11:00:43 UTC
Description of problem:
The 659a4348baaad2a09128251bb782c73f46875571 imported the logging.[ch] from gnupg, but it did not import the configure checks for inet_pton() so it is using inet_addr() unconditionally.

This can be demonstrated with running rpminspect on the binary RPM, where the "badfunc" check reports this "bad function".

Solved with the patch from upstream as reported here: https://dev.gnupg.org/T5720

Version-Release number of selected component (if applicable):
libgpg-error-1.42-4

How reproducible:
always

Steps to Reproduce:
1. run rpminspect on binary packages of the above version

Actual results:
the bad function inet_addr() reported

Expected results:
no failures

Additional info:

Comment 1 Jakub Jelen 2021-12-07 11:03:51 UTC
CentOS Stream 9 PR: https://gitlab.com/redhat/centos-stream/rpms/libgpg-error/-/merge_requests/3

Comment 7 errata-xmlrpc 2022-05-17 16:00:05 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 (new packages: libgpg-error), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHBA-2022:4009


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