home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!lll-winken!elroy.jpl.nasa.gov!sdd.hp.com!swrinde!gatech!paladin.american.edu!auvm!UNC.BITNET!URJLEW
- From: URJLEW@UNC.BITNET (Rostyslaw J. Lewyckyj)
- Newsgroups: bit.listserv.ibm-main
- Subject: Re: Addr: RACF/VM
- Message-ID: <IBM-MAIN%92101612371608@RICEVM1.RICE.EDU>
- Date: 16 Oct 92 17:34:00 GMT
- Sender: IBM Mainframe Discussion list <IBM-MAIN@RICEVM1.BITNET>
- Lines: 8
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
-
- Suppose someone sits and monitors the valid userid file.
- As soon as that changes, indicating a new userid has been added,
- this person quick logs on with that userid and the default password,
- and changes it to a password of their choice.
- Now the proper owner of the userid is locked out.
- How does one prevent this unless one presets the password for the
- new userids to something which only the requester and the admini-
- strator know about?
-