Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!pollux.usc.edu!kjh
From: kjh@pollux.usc.edu (Kenneth J. Hendrickson)
Newsgroups: comp.os.minix
Subject: Re: Crypt()
Message-ID: <25633@usc.edu>
Date: 1 Jul 90 06:13:33 GMT
References: <22918@nigel.udel.EDU> <1990Jun29.222218.4942@siia.mv.com> <25628@usc.edu>
Sender: news@usc.edu
Organization: EE-Systems, USC, Los Angeles
Lines: 23

In article <25628@usc.edu> kjh@pollux.usc.edu (Kenneth J. Hendrickson) writes:
>	After one failed login attempt (due to bad username or passwd),
>	Nobody can ever log in again!  Not even with a good passwd!

Investigation has revealed the following:

(1) Successive calls to crypt() in minix return different values,
    even with the same inputs to crypt().

(2) Successive calls to crypt() on several different BSD boxes return
    exactly the same values every time, with the same inputs to crypt().

(3) Minix seems to call crypt() in login.c in exactly the same way that
    the BSD boxes call crypt() in login.c.

(4) Crypt() itself does not change any of the variables declared static
    and defined outside of any function.  There is no indication that
    the crypt() I have is destroying itself at runtime.

HELP!  Something really obscure is happening here, and I would still
appreciate any pointers.  (I didn't get any with my last request.)

Ken Hendrickson N8DGN/6      kjh@usc.edu      ...!uunet!usc!pollux!kjh