File: README.Debian

package info (click to toggle)
crack 5.0a-12
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 9,016 kB
  • sloc: ansic: 7,444; perl: 1,375; sh: 1,062; makefile: 218
file content (47 lines) | stat: -rw-r--r-- 2,040 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
crack for Debian
----------------

Debian passwd files are usually *NOT* merged so you *cannot* run
# Crack /etc/passwd

However, the Crack wrapper script has been modified to consider
this case and run the merge scripts by itself and then run Crack
on the merged file.

If you are using MD5 passwords you need to install the 'crack-md5'
package (not 'crack'), please read the documentation
(/usr/share/doc/crack-common/manual.txt)

BTW, if you have a mixed crypt/md5 environment Crack will probably not work 
100% fine. Period. You can install first the 'crack' package, run
Crack  (it will probably have problems with the Md5 passwords). Once
it's finished (if ever) you should install 'crack-md5' and run it again.
The package maintainer could probably provide a better way to handle
this situation in the future but for now it's the only thing you can do
(save, perhaps, fixing the code so Crack works with *both* MD5 and DES).

Crack needs root privileges to run. It will not work from ordinary user
account. This is due to access permissions to /usr/share/Crack. Anyway -- you
wouldn't want your users to run Crack on your machine, would you?

There probably are errors due to the way it generates the binary-stamps
(since it uses uname to know which binaries it has compiled). I've
made changes to the script/binstamps so it always return 'debian'
when running on a Debian system. 

Also, binaries are under /usr/lib/Crack (with a symlink under 
/usr/share/Crack/run/bin/debian to keep Crack happy) to follow the FHS


TODO:

- write manpage
- fix lintian warnings (errors regarding xdawg are not errors, please
  see the changelog)
- add an init.d script so you can stop all password cracking processes
  (and rerun them if there is anyone pending on bootup). This will also help
  on upgrades (if any) since these processes should be stopped/restarted in
  this cases.

 -- Javier Fernández-Sanguino Peña <jfs@computer.org>, Wed,  4 Sep 2002 14:28:19 +0200,
    Paweł Więcek <coven@debian.org>, Sun, 13 Oct 2002 21:05:38 +0200