Bug 54097

Summary: [nis] Non-local yppasswd(1) -d broken in 5.1-CURRENT
Product: Base System Reporter: robert <robert>
Component: binAssignee: Marcelo Araujo <araujo>
Status: Closed Unable to Reproduce    
Severity: Affects Only Me CC: araujo
Priority: Normal    
Version: 5.1-CURRENT   
Hardware: Any   
OS: Any   

Description robert 2003-07-04 16:00:33 UTC 
The yppasswd command supports command the ability to override the local
YP/NIS configuration to permit password changes for non-local NIS
domains.  This is done using arguments that allow you to specify the
domain name and server name on the yppasswd command line.  In -STABLE,
this works properly; in -CURRENT, yppasswd incorrectly requires that
the user exist locally in order to change the remote password.

Fix: 

Sounds like we need special-case handling of the non-local NIS password
changing path in -CURRENT to avoid the local user check.  This should
be keyed on the use of the "-d" argument.
How-To-Repeat: 
-CURRENT:

paprika# yppasswd -y -d boltsys.com -h artemis.boltsys.com robert
yppasswd: robert: no such user

-STABLE:

pemaquid:~> yppasswd -y -d boltsys.com -h artemis.boltsys.com robert
Changing NIS password for robert on artemis.boltsys.com.
Old Password:
Comment 1 Robert Watson freebsd_committer freebsd_triage 2003-07-04 16:07:39 UTC 
On Fri, 4 Jul 2003, Robert Watson wrote:

> >How-To-Repeat:
> 
> -CURRENT:
> 
> paprika# yppasswd -y -d boltsys.com -h artemis.boltsys.com robert
> yppasswd: robert: no such user
> 
> -STABLE:
> 
> pemaquid:~> yppasswd -y -d boltsys.com -h artemis.boltsys.com robert
> Changing NIS password for robert on artemis.boltsys.com.
> Old Password: 

To clarify, in fact this bug exists in both -STABLE and -CURRENT; I
misreported because I didn't realize there was a local robert@ user on
pemaquid.  That said, it would still be very nice if this worked. :-)

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert@fledge.watson.org      Network Associates Laboratories
Comment 2 Marcelo Araujo freebsd_committer freebsd_triage 2016-12-28 12:46:54 UTC 
I can't reproduce this problem.