Path: utzoo!attcan!uunet!decwrl!sdd.hp.com!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!uw-beaver!ubc-cs!news-server.csri.toronto.edu!helios.physics.utoronto.ca!alchemy.chem.utoronto.ca!system From: system@alchemy.chem.utoronto.ca (System Admin (Mike Peterson)) Newsgroups: comp.sys.apollo Subject: Re: Password aging Summary: Broken at SR10.2 Message-ID: <1990Sep23.150137.21095@alchemy.chem.utoronto.ca> Date: 23 Sep 90 15:01:37 GMT References: <4ceda9bb.12c9a@digital.sps.mot.com> Organization: University of Toronto Chemistry Department Lines: 27 In article collins@nvpna1.prl.philips.nl (Donal O Coileain) writes: >In <4ceda9bb.12c9a@digital.sps.mot.com> chen@digital.sps.mot.com (Jinfu Chen) writes: >>Now it seems password aging still doesn't work under SR10.2. However, the >>result is a bit different. When I log on to a console, DM asks a new password >>and re-enter to verify it. So far so good, however, after a while DM returns >>an error, "Too many tries, password not changed". > >>Does anyone know if this is my setup problem or it's a bug? If so does >>SR10.3 fix already? > >I suspect it may be a setup problem. We have set the password lifespan >option at this site and it works. We also run sr10.2. Password aging/expiry works sometimes at SR10.2, especially if you login on the display. Sometimes it actually changes the password, sometimes it gives up. If you run X Windows by default at login, it will cause the login xterm to be killed every time that a new password is requested, but you can get another xterm from the window manager. If your master registry is on a DN10000 (like ours), it does not work most of the time, even on the display (SR10.2.p has no where near all the bug fixes / enhancements of SR10.2). It never works for telnet/rlogin logins. This is a known problem and it is supposed to work at SR10.3. -- Mike Peterson, System Administrator, U/Toronto Department of Chemistry E-mail: system@alchemy.chem.utoronto.ca Tel: (416) 978-7094 Fax: (416) 978-8775