Bug 1722832

Summary:	glibc: Avoid ABI exposure of the NSS service_user type
Product:	[Fedora] Fedora	Reporter:	Florian Weimer <fweimer>
Component:	glibc	Assignee:	Florian Weimer <fweimer>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	30	CC:	aoliva, arjun.is, codonell, dj, fweimer, law, mfabian, pfrankli, rth, siddhesh
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glibc-2.29.9000-19.fc31 glibc-2.29-18.fc30	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1710894	Environment:
Last Closed:	2019-09-21 05:46:39 UTC	Type:	---
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:
Bug Blocks:	1710894

Description Florian Weimer 2019-06-21 12:34:39 UTC

+++ This bug was initially created as a clone of Bug #1710894 +++

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 1 Fedora Update System 2019-09-05 09:20:15 UTC

FEDORA-2019-2e9a65b50a has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-2e9a65b50a

Comment 2 Fedora Update System 2019-09-05 12:53:23 UTC

glibc-2.29-22.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-2e9a65b50a

Comment 3 Fedora Update System 2019-09-06 09:44:21 UTC

FEDORA-2019-8532718f88 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-8532718f88

Comment 4 Fedora Update System 2019-09-06 12:33:57 UTC

glibc-2.29-22.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

Comment 5 Fedora Update System 2019-09-06 13:21:49 UTC

glibc-2.28-39.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-8532718f88

Comment 6 Fedora Update System 2019-09-21 01:42:19 UTC

glibc-2.28-39.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.