www.pudn.com > AntiCrack.zip > INSTALL

To install and use AntiCrack, please follow the steps 1-6 below: 
 
	1. Get the AntiCrack package (this package) 
	2. Get the Crack v4.1f package 
	3. Unbundle the Crack package 
	4. Unbundle the AntiCrack package in the Crack directory 
	5. Do "make" 
	6. Use AntiCrack 
 
And some more information will be found in the following sections 
 
	A. Tailoring AntiCrack 
	B. Some other feature 
	C. Feedback to the author 
 
of this file. 
 
1. GET THE ANTICRACK PACKAGE 
 
You already have the AntiCrack package because you see this file. :-) 
You can get the newest version of this package from the AntiCrack Home Page: 
 
	 
 
From now, I assume that the name of the package file "anticrack-1.11.tar.gz", 
and that you have the file in your home directory for easiness of 
explanation. 
 
2. GET THE CRACK v4.1f PACKAGE 
 
You need the Crack v4.1f package to make AntiCrack (another version of 
Crack might work, but what I work with is only this (v4.1f) version). 
You can get the package from: 
 
	 
 
I assume the Crack package file "crack_4.1.tar.Z" is in your home directory. 
 
3. UNBUNDLE THE CRACK PACKAGE 
 
To unbundle the Crack package, make an appropriate directory 
("crack", for example) and do the following: 
 
    % cd crack 
    % gunzip < $HOME/crack_4.1.tar.Z | tar xvf - 
 
($HOME means your home directory; you might specify another directory 
 according to in which directory you have the Crack package file.) 
 
then several files and directories will be created like this: 
 
    % ls 
    APPENDIX    DictSrc/    LICENCE     Runtime/    TODO 
    BUGS        Dicts/      MANIFEST    Scripts/ 
    Crack*      Docs/       README      Sources/ 
    % 
 
4. UNBUNDLE THE ANTICRACK PACKAGE IN THE CRACK DIRECTORY 
 
Now let us unbundle the AntiCrack package.  For easiness of compilation, 
unbundle it in the Crack directory. 
 
    % gunzip < $HOME/anticrack-1.11.tar.gz | tar xvf - 
 
Then you will see the directory "AntiCrack" is created. 
 
    % ls 
    APPENDIX    Crack*      Docs/       README      Sources/ 
    AntiCrack/  DictSrc/    LICENCE     Runtime/    TODO 
    BUGS        Dicts/      MANIFEST    Scripts/ 
    % 
 
5. DO "MAKE" 
 
To compile AntiCrack, change directory to "AntiCrack" and type "make". 
 
    % cd AntiCrack 
    % make 
 
Now we have AntiCrack program named "anticrack". 
 
6. USE ANTICRACK 
 
To use AntiCrack, you need "rule file" and "dictionary file". 
For quick use, you can use Crack's rule file and the operating system's 
standard dictionary (e.g., /usr/dict/words or /usr/share/dict/words or 
anything) by doing like this: 
 
    % ./anticrack ../Scripts/dicts.rules /usr/dict/words 
 
AntiCrack asks you to input your password candidate. 
 
    % ./anticrack ../Scripts/dicts.rules /usr/dict/words 
    Welcome to AntiCrack. 
    Your password candidate:  
 
Please type your password candidate and return.  Echo is off here, 
so you do not see what you type.  Then AntiCrack asks it again 
 
    Type it again:  
 
and type the same password candidate once again and return. 
 
You will wait for some time (a few ten seconds or a few minutes 
according to the machine power and your password candidate). 
 
If the password candidate will be cracked by the specified rules 
and the dictionary, AntiCrack shows the following message: 
 
    Cracked. Try another candidate. 
 
In this case, you should NOT use the password candidate as 
your password. 
 
If the password candidate will not cracked by the specified rules 
and the dictionary, AntiCrack shows the message: 
 
    Not Cracked. 
 
In this case, the password candidate will be a good choice 
for your password.  But... 
 
    Whether a password is cracked or not depends on what rules and 
    what dictionary to use for cracking, so even if AntiCrack says 
    your password candidate is "Not Cracked", it does NOT mean "SAFE." 
 
If you have more "powerful" rules and a huge dictionary, checking 
will be more thorough, but it will take a lot of time.  So this is 
trade-off. 
 
A. TAILORING ANTICRACK 
 
You can tailor the rule file and adopt any dictionary file. 
The format of the rule file is explained in "dicts.rules" file of 
the Crack package (resides in Scripts/ directory).  A dictionary 
file is simply a list of words (cf. /usr/dict/words). 
 
Password checking time of AntiCrack is roughly proportional to 
(the number of rules) times (the number of words in the dictionary). 
So you should decide what rules to include in the rule file and 
what dictionary to use according to the machine power you have 
and how thorough you want to check your password. 
 
B. SOME OTHER FEATURE 
 
AntiCrack shows a terse help by typing: 
 
    % ./anticrack 
 
Some options will show how AntiCrack is working.  If you are interested 
in how AntiCrack works, you can use these options.  But please be careful, 
these options will show what you typed as your password candidate! 
 
C. FEEDBACK TO THE AUTHOR 
 
Any comments, suggestions, bug fixed are welcome.  Please contact me 
via e-mail.  My e-mail address is 
 
	tominaga@cc.teu.ac.jp 
 
I hope you enjoy this software! 
 
 -- tominaga