🚀 go-pugleaf

In article <1992Sep21.092710.18030@aston.ac.uk> evansmp@uhura.aston.ac.uk (Mark Evans) writes:
|jim@ferkel.ucsb.edu (Jim Lick) writes:
|: 
|: From the user's perspective, this seems to be an unfair policy.  How is J.
|: Random User going to know that the password they enter is easily cracked?
|: Besides, this problem can be solved much more easily by using a passwd
|: program which disallows use of crackable passwords.  As it is, you are
|: trying to catch the problem after it's happened.
|
|This dosn't work to well, because it can easily result in people
|writing the passwords down.

This depends on how `arcane' the password program insists the passwords be.
A fairly simple set of heuristics, or simply a run through the cracker
as part of selecting a password, leaves a great many memorable passowrds
available.  (The main problem is for systems that are only used occasionally,
there it is often difficult to remember even a memorable password).
-- 
sarima@teradata.com			(formerly tdatirv!sarima)
  or
Stanley.Friesen@ElSegundoCA.ncr.com