🚀 go-pugleaf

daniel@vcp1.vcp.monash.edu.au writes:
}The only solution I could find would be to limit the frequency of
}reading the passwd file, say to once per second.  Only on larger
}systems where 50 people try to login at the same time (and how often
}does that happen?) would such a limit cause inconvenience.

In the "real world" I suppose it happens every day at 8am,
here it happens on the hour from about 9 am to 4pm (nobody
wants an 8am class ;-)

}Can anyone comment on the practicality, viablility and added security
}of such a beastie?

I think more useful, and less obtrusive, is a system that given
more than L attempts on a given password in the last M minutes
always returns failure (until N more minutes pass quietly).
[L, M & N configurable by the sysadmin]

John
-- 
John Hascall                                       ``Live with it pink-boy!''
Project Vincent                                                              
Iowa State University Computation Center                     john@iastate.edu
Ames, IA  50011                                      515/294-9551 [fax -1717]