Bug 28645 - NIS does not work with new glibc 2.32. libnss_nis is needed.
Summary: NIS does not work with new glibc 2.32. libnss_nis is needed.
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: New RPM package request (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA8-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2021-03-25 22:13 CET by marco tux4ever
Modified: 2021-04-24 00:54 CEST (History)
3 users (show)

See Also:
Source RPM: nss_nis
CVE:
Status comment:


Attachments

Description marco tux4ever 2021-03-25 22:13:33 CET
NIS does not work with new glibc 2.32
nss_nis is missing.
if you configure nis in /etc/nsswitch.conf and use ypbind-2.7.2-3.1 (now in update_testing) ypbind is working correctly, but the maps of ypserver are not use.

nss_nis or libnss_nis  is needed for nis to work. 

cf : 
https://github.com/thkukuk/libnss_nis
Comment 1 David GEIGER 2021-03-26 07:39:03 CET
cc'ing tmb to have his opinion :)

CC: (none) => geiger.david68210, tmb

Comment 2 marco tux4ever 2021-03-26 18:49:20 CET
with nss_nis-3.1-6.fc33.x86_64.rpm and ypbind-2.7.2-3.1 nis is working and I did not find a bug.
Comment 3 Thomas Backlund 2021-03-26 19:17:04 CET
yeah, I suspected we might be missing some nis bits when we switched to new glibc,
but I did not dig into all bits as I dont use it and I wasn't sure we had users of it...

but as we now have it confirmed we missed some bits, and people need and actually use it, we need to introduce it in Cauldron and mga 8 updates
Comment 4 Lewis Smith 2021-03-26 21:40:51 CET
Thanks for taking this on, Thomas.
Excuse me assigning it to you in the light of the previous comment.

Assignee: bugsquad => tmb

Comment 5 marco tux4ever 2021-04-11 22:35:12 CEST
Hello, is there some news about nss_nis ? For now I'm using nss_nis-3.1-6.fc33.x86_64.rpm but this is still a bad workaround. Thank you all for the work.
Comment 6 Thomas Backlund 2021-04-12 10:52:33 CEST
Sorry, I got sidetracked fixing other issues...

I've just built:

SRPM:
nss_nis-3.1-1.mga8.src.rpm

i586:
libnss_nis2-3.1-1.mga8.i586.rpm

x86_64:
lib64nss_nis2-3.1-1.mga8.x86_64.rpm


please test if it works
Comment 7 marco tux4ever 2021-04-19 11:34:47 CEST
I've just tested it. It works fine ! 
Thanks for all.
Comment 8 Thomas Backlund 2021-04-19 14:11:46 CEST
(In reply to marco tux4ever from comment #7)
> I've just tested it. It works fine ! 
> Thanks for all.

Great to hear

and I assume you tested the x86_64 rpm ?
Comment 9 marco tux4ever 2021-04-22 10:21:46 CEST
--> and I assume you tested the x86_64 rpm ? :
Yes that's it. I didn't have a way to test the i586.rpm.
Comment 10 Thomas Backlund 2021-04-22 10:47:48 CEST
(In reply to marco tux4ever from comment #9)
> --> and I assume you tested the x86_64 rpm ? :
> Yes that's it. I didn't have a way to test the i586.rpm.

No worries about that, it's just so we know what arch it's tested & known to work on before validating it and pushing to updates
Comment 11 Thomas Backlund 2021-04-23 23:49:47 CEST
validating based on comment 7 and comment 9.

Whiteboard: (none) => MGA8-64-OK
Assignee: tmb => qa-bugs
Keywords: (none) => advisory, validated_update
CC: (none) => sysadmin-bugs

Comment 12 Mageia Robot 2021-04-24 00:54:41 CEST
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2021-0093.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED


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