Bug 1710894

Summary: glibc: Avoid ABI exposure of the NSS service_user type
Product: Red Hat Enterprise Linux 8 Reporter: Florian Weimer <fweimer>
Component: glibcAssignee: DJ Delorie <dj>
Status: CLOSED ERRATA QA Contact: qe-baseos-tools-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.1CC: ashankar, codonell, dj, fweimer, mnewsome, pfrankli, skolosov
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glibc-2.28-64.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1722832 (view as bug list) Environment:
Last Closed: 2019-11-05 21:29: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:
Bug Depends On: 1722832    
Bug Blocks: 132608, 1684559    

Description Florian Weimer 2019-05-16 14:09:56 UTC 
We should backport this patch in preparation of a potential future fix for bug 132608 later in the life-cycle of Red Hat Enterprise Linux 8.

commit a9368c34d70cef91ca59b09941f496df11d6b146
Author: Florian Weimer <fweimer>
Date:   Wed May 15 13:51:35 2019 +0200

    nss: Turn __nss_database_lookup into a compatibility symbol
    
    The function uses the internal service_user type, so it is not
    really usable from the outside of glibc.  Rename the function
    to __nss_database_lookup2 for internal use, and change
    __nss_database_lookup to always indicate failure to the caller.
    
    __nss_next already was a compatibility symbol.  The new
    implementation always fails and no longer calls __nss_next2.
    
    unscd, the alternative nscd implementation, does not use
    __nss_database_lookup, so it is not affected by this change.
Comment 2 Sergey Kolosov 2019-07-24 17:09:37 UTC 
Verified,
glibc-2.28-64.el8 has __nss_database_lookup2 symbol and it has __nss_database_lookup as compat one.
Comment 4 errata-xmlrpc 2019-11-05 21:29: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, 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/RHSA-2019:3513