From owner-freebsd-hackers Wed Oct 23 02:54:17 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA09067 for hackers-outgoing; Wed, 23 Oct 1996 02:54:17 -0700 (PDT) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.225.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA09061 for ; Wed, 23 Oct 1996 02:54:14 -0700 (PDT) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id KAA03380 for ; Wed, 23 Oct 1996 10:53:35 +0100 Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id KAA26052 for freebsd-hackers@freefall.cdrom.com; Wed, 23 Oct 1996 10:58:30 +0100 Date: Wed, 23 Oct 1996 10:58:30 +0100 From: Christoph Kukulies Message-Id: <199610230958.KAA26052@gilberto.physik.rwth-aachen.de> To: freebsd-hackers@freefall.FreeBSD.org Subject: NIS passwd probs Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk That mastername vs. myname discrepancies left aside I kludged yppasswdd so that it stays running and changing the NIS password on the client side give a strange picture: Changing the NIS password (using passwd - freshly compiled) on a client is formally accepted the first time. But trying to use it afterwards fails. The old password is still valid. Trying the to change the password again to something different on the client (typing the newly altered password at the Old Password: prompt) fails immediately with: Changing NIS password for joeuser on nisserver@domain. Old Password: passwd: Sorry. This wan't accompanied with any syslog activity (I was watching /var/log /messages at that time). Using the old (unaltered) password at the Old Password: prompt now also gives 'Sorry'. The whole passwd issue (root and user passwords setting on the client side) is a pending problem here at our site and I really wonder if this is a problem with FreeBSDs NIS in general or a problem with my site's setup. Sure, there are lurking pitfalls with building the world on the server and running perhaps outdated clients but I'm trying to keep that matched at least in the field of my experimenting at the moment. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de