Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!uunet!spool.mu.edu!caen!hellgate.utah.edu!fcom.cc.utah.edu!cs.weber.edu!terry
From: terry@cs.weber.edu (A Wizard of Earth C)
Subject: Re: xlock won't recognize password
Message-ID: <1992Oct1.031230.4671@fcom.cc.utah.edu>
Sender: news@fcom.cc.utah.edu
Organization: Weber State University (Ogden, UT)
References: <1992Sep29.222158.13275@mel.dit.csiro.au>
Date: Thu, 1 Oct 92 03:12:30 GMT
Lines: 32
In article <1992Sep29.222158.13275@mel.dit.csiro.au> tim@kimba.catt.citri.edu.au (Tim Liddelow) writes:
>Hi all. I compiled up a X11R5 raw version of xlock from the X contrib
>directory at one of the X mirror sites here. The problem is that it compiled
>up pretty well fine, but it won't recognize my password. Now could this be
>anything to do with crypt() I added to the standard C library ? Or can't
>it handle the shadow password entries (surely that would be built in to
>the system calls.)
Yes, the problem is crypt(). You need to rebuild passwd, chfn, chpass,
and the lib routines that depend on crypt() (for the most part). Then
you need to rebuild your password database and reassign passwords.
The problem is that the existing passwords aren't crypted and so the crypted
password from xlock (using the 1st 2 characters of the user's password as
the salt) doesn't match the remainder of the user's password. This isn't
suprising.
Sorry; I don't have a list of all the executables that use password file
related functions; yet another reason to have shared libraries.
Terry Lambert
terry@icarus.weber.edu
terry_lambert@novell.com
---
Any opinions in this posting are my own and not those of my present
or previous employers.
--
-------------------------------------------------------------------------------
"I have an 8 user poetic license" - me
Get the 386bsd FAQ from agate.berkeley.edu:/pub/386BSD/386bsd-0.1/unofficial
-------------------------------------------------------------------------------