Package: libnssswitch-nis
Version: 3.1-4
Severity: grave
It seems that currently unstable has a totally not working NIS binding for
users. I
performed my trials using an existing setup (bullseye-based NIS master+slaves
and
clients network in the real life).
I recently upgraded a bullseye NIS client box to sid for testing and discovered
that while
ypbind-mt is regularly working, the usual mapping of NIS users has gone.
To be sure of the issue I prepared a vagrant bullseye VM and bound that to
the regular bullseye NIS master as usual: perfectly working.
Then I full-upgraded to sid with the same broken result:
vagrant@debian:/etc$ ypcat passwd
[...]
lovergine:x:2003:2000:Francesco Lovergine (trial),,,:/home/lovergine:/bin/bash
[...]
{sorry, I stripped the full output for privacy)
vagrant@debian:/etc$ id lovergine
id: ‘lovergine’: no such user
vagrant@debian:/etc$ cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# If you have the `glibc-doc-reference' and `info' packages installed, try:
# `info libc "Name Service Switch"' for information about this file.
passwd: compat systemd
group: compat systemd
shadow: compat
gshadow: compat
hosts: files dns
networks: files
protocols: db files
services: db files
ethers: db files
rpc: db files
netgroup: nis
vagrant@debian:/etc$ cat /etc/passwd
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin
man:x:6:12:man:/var/cache/man:/usr/sbin/nologin
lp:x:7:7:lp:/var/spool/lpd:/usr/sbin/nologin
mail:x:8:8:mail:/var/mail:/usr/sbin/nologin
news:x:9:9:news:/var/spool/news:/usr/sbin/nologin
uucp:x:10:10:uucp:/var/spool/uucp:/usr/sbin/nologin
proxy:x:13:13:proxy:/bin:/usr/sbin/nologin
www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin
backup:x:34:34:backup:/var/backups:/usr/sbin/nologin
list:x:38:38:Mailing List Manager:/var/list:/usr/sbin/nologin
irc:x:39:39:ircd:/run/ircd:/usr/sbin/nologin
gnats:x:41:41:Gnats Bug-Reporting System
(admin):/var/lib/gnats:/usr/sbin/nologin
nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin
_apt:x:100:65534::/nonexistent:/usr/sbin/nologin
systemd-timesync:x:101:101:systemd Time
Synchronization,,,:/run/systemd:/usr/sbin/nologin
systemd-network:x:102:103:systemd Network
Management,,,:/run/systemd:/usr/sbin/nologin
systemd-resolve:x:103:104:systemd Resolver,,,:/run/systemd:/usr/sbin/nologin
messagebus:x:104:105::/nonexistent:/usr/sbin/nologin
_chrony:x:105:112:Chrony daemon,,,:/var/lib/chrony:/usr/sbin/nologin
sshd:x:106:65534::/run/sshd:/usr/sbin/nologin
vagrant:x:1000:1000::/home/vagrant:/bin/bash
systemd-coredump:x:999:999:systemd Core Dumper:/:/usr/sbin/nologin
_rpc:x:107:65534::/run/rpcbind:/usr/sbin/nologin
+::::::
My next step will be running a full-sid setup for a test network, but I don't
see any reason why the working NIS maps could be broken, my guess is that
the problem is connected to some inner libnss/libc issue.
-cheers
--
Francesco P. Lovergine
