home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.sun.admin:5913 comp.unix.aix:9174
- Newsgroups: comp.sys.sun.admin,comp.unix.aix
- Path: sparky!uunet!mcsun!sun4nl!fwi.uva.nl!casper
- From: casper@fwi.uva.nl (Casper H.S. Dik)
- Subject: Re: RPC error using yppasswd
- Message-ID: <1992Aug28.075152.22732@fwi.uva.nl>
- Sender: news@fwi.uva.nl
- Nntp-Posting-Host: adam.fwi.uva.nl
- Organization: FWI, University of Amsterdam
- References: <1992Aug26.094155.526@idiws1.idi.battelle.org>
- Date: Fri, 28 Aug 1992 07:51:52 GMT
- Lines: 35
-
- newsmgr@idiws1.idi.battelle.org writes:
-
- >Hello, we have a NIS/NFS setup with a Sun workstation running 4.1.2 as
- >the NIS server.
-
- >A user on a Rs6000 running AIX v3.2 with cumlative patch tape of 9 Aug installed
- >attempts a yyppasswd:
-
- >% yppasswd
- >Changing NIS password for willie
- >Old NIS password:
- >New password:
- >Retype new password:
- >RPC: Server can't decode arguments
- >couldn't change passwd
-
- >What does that RPC error mean? At the time the Sun system was slow due to
- >heavy load I could do a yyppasswd with my own account.
-
- >Thanks!
-
- If it happens every time this particular user uses yppasswd, it
- is probaly due to a bug in rpc.yppasswdd. It uses a function to
- check the length and validity of the arguments. For the gecos and
- shell fields, it is obvious they have a maximum length and a restricted
- character set. The stupid thing is that the cleartext old password which
- is also transmitted as a check, is also checked against similar restrictions.
-
- My guess is that this user has a current password with control characters
- or a ':' in it. Locally, I've nop'ped out this test on the old password.
-
- Casper
- --
- | Casper H.S. Dik
- | casper@fwi.uva.nl
-