From owner-freebsd-bugs@FreeBSD.ORG Wed Apr 21 00:41:17 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB96416A4CE; Wed, 21 Apr 2004 00:41:17 -0700 (PDT) Received: from smtp.infracaninophile.co.uk (happy-idiot-talk.infracaninophile.co.uk [81.2.69.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46BE443D2F; Wed, 21 Apr 2004 00:41:16 -0700 (PDT) (envelope-from m.seaman@infracaninophile.co.uk) Received: from happy-idiot-talk.infracaninophile.co.uk (localhost.infracaninophile.co.uk [IPv6:::1])i3L7fBIb041935 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Apr 2004 08:41:11 +0100 (BST) (envelope-from matthew@happy-idiot-talk.infracaninophile.co.uk) Received: (from matthew@localhost)id i3L7f9GB041934; Wed, 21 Apr 2004 08:41:09 +0100 (BST) (envelope-from matthew) Date: Wed, 21 Apr 2004 08:41:09 +0100 From: Matthew Seaman To: "Jin Guojun [NCS]" Message-ID: <20040421074109.GA41275@happy-idiot-talk.infracaninophile.co.uk> Mail-Followup-To: Matthew Seaman , "Jin Guojun [NCS]" , questions@freebsd.org, bugs@freebsd.org References: <4085889D.C5EA07D7@lbl.gov> <40859A57.68F03A90@lbl.gov> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline In-Reply-To: <40859A57.68F03A90@lbl.gov> User-Agent: Mutt/1.5.6i X-Virus-Scanned: clamd / ClamAV version devel-20040420, clamav-milter version 0.70k X-Spam-Status: No, hits=-4.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on happy-idiot-talk.infracaninophile.co.uk cc: bugs@freebsd.org cc: questions@freebsd.org Subject: Re: what things can cause yppasswd failure? X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Apr 2004 07:41:18 -0000 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 20, 2004 at 02:47:03PM -0700, Jin Guojun [NCS] wrote: > "Jin Guojun [NCS]" wrote: >=20 > > We have experience very strange problem on using NIS over FreeBSD 4.x a= nd 5.x. > > Some uses can change passwd where other users cannot. > > > > case 1: Use FreeBSD 5.1 as NIS server -- NIS client is a FreeBSD 4.9= host > > I can change my passwd any time and any where, and most people cannot. > > If I change my home directory to anywhere else in the master.passwd fil= e, > > re-make in /var/yp directory, then I cannot change my passwd any more. > > It causes yppasswdd dying on signal 11, which most users encountered. > > > > case 2: Use FreeBSD 4.10-BETA as NIS server -- same NIS client > > I have no problem to change passwd, other users do. Failure will not > > kill yppasswdd, but it returns following error: > > > > passwd: failed to change NIS password: RPC: Server can't decode argumen= ts > > > > After this message I still can change my passwd. Also, changing my home > > directory in /var/yp/master.passwd and re-making DO NOT AFFECT > > me to change passwd. >=20 > By searching mail archive, I did not find related problem. > This is what we found: >=20 > If users login with bash, these users are not able to change their pa= sswd. > The error is: >=20 > passwd: failed to change NIS password: RPC: Server can't decode argum= ents >=20 > Probably bash is not part of default FreeBSD syste, NIS system has not be= en > tested > with bash for changing password. Interesting: nice work deducing that. This is clearly a bug -- certainly if rpc.yppasswdd dies with a SEGV, which should never happen. Please do report this problem via send-pr(1). However, I think there must be something different about your systems, as bash(1) is a popular shell and if this was a general problem I should think someone would have complained about it by now. Does this apply to other shells than bash -- eg zsh(1), ksh(1)? Does using the '-v' (verbose logging) flag on rpc.yppasswdd get you any more information? Does this still apply if there's an entry for bash in /etc/shells on the NIS server? Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAhiWVdtESqEQa7a0RAsboAJ9ES+hAagm1kWtYqqqw7CjcTvIF/QCfaeAB vUZ9zEi20NpFWtBYlXtV+yA= =h4tE -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c--