Re: Problem with npasswd??

Article View: comp.security.misc

Article #76

Back to comp.security.misc Previous Next

#76

From: Drew Solomon
Date: Sat, 01 Aug 1992 13:06

20 lines
1359 bytes

In article <12396@ecs.soton.ac.uk> tjc@ecs.soton.ac.uk (Tim Chown) writes:
>In <1992Jul28.035951.22683@reed.edu> nelson@reed.edu (Nelson Minar) writes:
>
>>Furthermore, there's no reason in principle that the crack 4.1 word
>>generation engine (which is excellent) can't be grafted into npasswd.
>>I keep hoping someone else will do the work for me.
>
>Why not just alter npasswd to force at least one upper case letter, one
>digit plus one non-alphanumeric?   Such passwords can still be remembered
>reasonably easily and are very resistant to cracking programs.  

Though one problem with the algorithm you've described is that the
password "h3llo!", which is legal by your rules, is also crackable.
A dictionary search would be required to determine if the password
they have chosen is still breakable.


-- 
Drew Solomon
solomon@caen.engin.umich.edu

Technical Details

Message-ID: <btW-06-@engin.umich.edu>

Path: arc1-ca.pugleaf.net!sparky!uunet!caen!solomon

References: <1992Jul27.184324.14697@hubcap.clemson.edu> <1992Jul28.035951.22683@reed.edu> <12396@ecs.soton.ac.uk>

Show Full Headers

Complete Article Headers

Newsgroups: comp.security.misc,alt.security,comp.unix.ultrix
Path: arc1-ca.pugleaf.net!sparky!uunet!caen!solomon
From: solomon@engin.umich.edu (Drew Solomon)
Subject: Re: Problem with npasswd??
Message-ID: <btW-06-@engin.umich.edu>
Date: Sat, 01 Aug 92 09:06:30 EDT
Organization: University of Michigan Engineering, Ann Arbor
References: <1992Jul27.184324.14697@hubcap.clemson.edu> <1992Jul28.035951.22683@reed.edu> <12396@ecs.soton.ac.uk>
Nntp-Posting-Host: apology.engin.umich.edu
Lines: 20

Reply to Parent Message