Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!mips!mips!sdd.hp.com!caen!destroyer!ubc-cs!uw-beaver!rice!news.Rice.edu!rich From: rich@Rice.edu (Richard Murphey) Subject: Re: crypt problems In-Reply-To: randy@chinet.chi.il.us's message of Mon, 10 Aug 1992 15:04:27 GMT Message-ID: <RICH.92Aug11102715@kappa.Rice.edu> Sender: news@rice.edu (News) Reply-To: Rich@rice.edu Organization: Department of Electrical and Computer Engineering, Rice University References: <BsrwJG.tq@chinet.chi.il.us> Date: Tue, 11 Aug 1992 16:27:15 GMT Lines: 23 In article <BsrwJG.tq@chinet.chi.il.us> randy@chinet.chi.il.us (Randy Suess) writes: I installed the crypt patches and re-compiled the files mentioned in a recent posting. My passwd files are now nicely encrypted. However, xdm (in the X11 release for bsd) will not recoginize a password typed in. If I remove the "*" in /etc/passwd, xdm will accept a null password. Obviously it knows nothing about the new bsd pseudo shadow files. Tried recompiling xdm, but no go. Also, if I rlogin into the bsd machine, it always asks for a passwd even if there is a .rhosts and a mention in /etc/hosts.equiv. I re-compiled rlogind, but again no go. Obviously there must be a library I need to re-compile so these programs recoginize the new form. Any ideas? Export restrictions apply to xdm and 386BSD alike, so the xdm binary on agate has the stock crypt_dummy.o compiled in. You need to recompile xdm when you install a real crypt and recompile login and friends. When you put the new crypt.o in libc.a, recompiling xdm with the new libc.a will fix xdm. xdm is designed to be run as root. You can either invoke it as root or `chown root xdm; chmod u+s xdm'. Rich --