Bug 129541 - [nis] passwd(1) cannot be forced to "yp" mode in some circumstances.
Summary: [nis] passwd(1) cannot be forced to "yp" mode in some circumstances.
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 6.4-STABLE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
Depends on:
Reported: 2008-12-10 02:40 UTC by Dan Mahoney
Modified: 2018-01-03 05:16 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Dan Mahoney 2008-12-10 02:40:01 UTC
"passwd" cannot be forced to NIS unless the machine is configured to use NIS for its own password file.

prime# passwd -y -d gushi-systems -h prime.gushi.org sdk
Changing local password for sdk
New Password:



None known.  This is an edge case, but it's feasibly possible that a server
could want to serve NIS without itself participating in it (via map files 
separate from its own).  Since ypcat and the like all still work, passwd
should (at least when forced) pick up similar hueristics.
Configure a server as an NIS master server, populate the maps, but do not
add the +:::::::: to /etc/passwd :

prime# ypcat master.passwd.byname|grep sdk
sdk:$1$1WZHl5y0$EjTF/5oH/4tiPJ2.ofGPn1:1084:1084::0:0:Xial Lunashine,,,8138326399:/home/sdk:/usr/local/bin/bash
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:58:33 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped