Bug 2029808

Summary: The libgpg-error is using old inet_addr() unconditionally
Product: Red Hat Enterprise Linux 9 Reporter: Jakub Jelen <jjelen>
Component: libgpg-errorAssignee: Jakub Jelen <jjelen>
Status: CLOSED ERRATA QA Contact: Stanislav Zidek <szidek>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 9.0Keywords: Triaged
Target Milestone: rc   
Target Release: 9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
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.
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-17 16:00:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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