Cisco Cisco MediaSense Release 9.1(1) Licensing Information

- after all that, it's PROBABLY a safe(-ish) password.  8-)

 

 

*** Instructions for building CrackLib...

 

 

STEP 0) Engage your brain.

 

I'm interested in improving the CrackLib software, doing bugfixes,

"guessing technique" improvements, and portability enhancements.

 

I'm NOT interested in unhelpful comments like "well, _my_ operating

system doesn't come with a dictionary".  If it doesn't, either complain

to your vendor, or GO AND GET a dictionary off the net.

 

CrackLib is NOT a TOOL.  It is not a complete package.  It is not

something you can utilise directly.

 

It is a resource, an aid, something to enhance the functionality of

other software.  You need to (either) write OR modify other software to

use it.  If you can't do this, then you shouldn't be wasting your time

with it.

 

Regarding bugs and portability problems: please try to work them out for

yourself, and then (please) TELL me about them.  This will help me

improve future versions.

 

 

STEP 1) Edit the Makefile to set your preferred value of DICTPATH

 

This it the directory+filename-prefix that your version of CrackLib will

go hunting for, and it must be visible to all programs on all hosts that

use CrackLib

 

Hence, if you want to use a CrackLib binary on a distributed network,

these files are probably best placed on an NFS server.

 

Note: You have to specify a FILENAME PREFIX too, eg:

 

DICTPATH=/usr/local/lib/pw_dict

 

which will generate:

 

/usr/local/lib/pw_dict.pwd

/usr/local/lib/pw_dict.pwi

/usr/local/lib/pw_dict.hwm

 

which are the files that CrackLib needs.