This version of john has two new conffiles for the mailer script:

/etc/john-mail.conf

---------------------

This is where you define the command used to send messages to users,

and the shells to be ignored when sending the messages. A working

example is already installed.

You can set the shells to be ignored, for example:

shells=-,/bin/false,/dev/null,/bin/sync,/usr/bin/falselogin

The default is set to:

shells=-,/bin/false,/dev/null,/bin/sync

And you may set the command used to send the message (the message

will be piped into this command):

mailcmd=/usr/sbin/sendmail

That is the default. If you use sendmail, or if your mailer provides

a "sendmail" executable, you may use the above line.

And if you want to pass extra arguments to your mailer, set

mailargs:

mailargs= ...

The default is not to define mailargs.

/etc/john-mail.msg

------------------

This is the message template to be sent to the user. In the message,

the strings @LOGIN and @HOSTNAME will be substituted for the user's

login and the host name.

If you use sendmail as mail command, you may include the headers

at the top of the template message, like this:

=============================================================

Subject: Gotcha!

Cc: root

Just cracked your password for account @LOGIN at @HOSTNAME.

Please change it.

John the Ripper.

=============================================================

You may also use some binary of yours as the mail command; then it

will be called, and the template (with the variables already

substituted) will be piped into it. This may be useful if you want

to use complex logging (using a DBMS, for example), or if you

want to automatically run scripts (that block the account,

perhaps?)

john (1.6-17) unstable; urgency=low

  * Rewording of comments in config file. (Closes: #115556)

    (Thanks to Martin F Krafft)

  * Included hack to remove cronjob if needed. (Closes: #114835,#117034)

 -- Christian Kurz <shorty@debian.org>  Sun, 14 Oct 2001 20:14:42 +0200

john (1.6-16) unstable; urgency=low

  * Integrated patch from Damyan Ivanov to fix unquoted sed 

    expressions. (Closes: #113557)

 -- Christian Kurz <shorty@debian.org>  Wed, 26 Sep 2001 12:57:53 +0200

john (1.6-15) unstable; urgency=low

  * Fixed typo in debconf templates. (Closes: #112058,#113166)

  * Should fix another problem with the lock-file. (Closes: #113332)

 -- Christian Kurz <shorty@debian.org>  Wed, 12 Sep 2001 16:08:30 +0200

john (1.6-14) unstable; urgency=low

  * Added german debconf translation from Sebastian Feltel.

    (Closes: #109980)

  * Fixed two typos in the john.1 manpage, noted by Stephen Frost.

  * Applied patch from Daniel Kobras to fix two oversights in the

    cronjob script. (Closes: #110272)

  * Applied patch from Jeronimo Pellegrini to fix some small problems

    in the scripts. (Closes: #110957)

 -- Christian Kurz <shorty@debian.org>  Sat, 25 Aug 2001 09:09:18 +0200

john (1.6-13) unstable; urgency=low

  * We'll gzip the example file, which is about 12k. But the other files

    which are just 2-6k will be stay uncompressed, until some very good

    reasons are presented to convince me. (Closes: #96650)

  * Integration of Patch from Jeronimo Pellegrini to support the

    installation and deinstallation of a cronjob. (Closes: #101970)

 -- Christian Kurz <shorty@debian.org>  Thu, 12 Jul 2001 22:55:09 +0200

john (1.6-12) unstable; urgency=low

  * Now we finally added manpages for john which have been written by

    Jordi Mallach and Jeronimo Pellegrini. (Closes: #62498)

  * Applied a patch from Jeronimo Pellegrini to make the mailer script

    more configurable. (Closes: #101968)

 -- Christian Kurz <shorty@debian.org>  Sun, 20 May 2001 10:18:56 +0200

john (1.6-11) unstable; urgency=low

  * Fixed Symlinks for $ARCHITECURE != i386. (Closes: #92280)

 -- Christian Kurz <shorty@debian.org>  Sat, 31 Mar 2001 18:34:42 +0200

john (1.6-10) unstable; urgency=low

  * Fixed the symlinks, since we didn't notice that we broke them with 

    the 1.6-8 release. Now, it should work fine again. (Closes: #91824)

 -- Christian Kurz <shorty@debian.org>  Wed, 28 Mar 2001 08:22:18 +0200

john (1.6-9) unstable; urgency=low

  * Fixed the name of the override file for john and also it'

    location. (Closes: #81218)

 -- Christian Kurz <shorty@debian.org>  Sun, 25 Mar 2001 00:30:33 +0100

john (1.6-8) unstable; urgency=low

  * Fixed the startup script for john to correctly use bash.

 -- Christian Kurz <shorty@debian.org>  Thu,  1 Mar 2001 20:00:13 +0100

john (1.6-7) unstable; urgency=low

  * Fixed a typo to build john also on Alpha (Closes: #83696)

 -- Christian Kurz <shorty@debian.org>  Sat, 27 Jan 2001 09:13:13 +0100

john (1.6-6) unstable; urgency=low

  * Added sparc-fix from Solar Designer (Closes: #81756).

  * Changed rules file to build two different versions of john, one with

    mmx extensions, and one without.

  * Added wrapper script to start john.

 -- Christian Kurz <shorty@debian.org>  Fri, 12 Jan 2001 22:31:05 +0100

john (1.6-5) unstable; urgency=low

  * Moved overrides file to correct location (Closes: 81218).

  * Added 3 lines to overrides file for the symlinks.

 -- Christian Kurz <shorty@debian.org>  Thu,  4 Jan 2001 20:51:32 +0100

john (1.6-4) unstable; urgency=low

  * Hopefully I fixed now the logfile-path-bug.

 -- Christian Kurz <shorty@debian.org>  Fri,  8 Dec 2000 22:26:26 +0100

john (1.6-3) unstable; urgency=low

  * Fixed pre-rm to allow removal of package (Closes: 74091).

 -- Christian Kurz <shorty@debian.org>  Thu,  5 Oct 2000 21:55:51 +0200

john (1.6-2) unstable; urgency=low

  * Changed debian/rules to be faster and more portable.

  * Fixed prerm-script to run only on purges.

  * Fixed some pathes to better defaults.

 -- Christian Kurz <shorty@getuid.com>  Mon, 15 May 2000 19:37:07 +0200

john (1.6-1) unstable; urgency=low

  * First Debian release.

 -- Christian Kurz <shorty@debian.org>  Sat,  1 Apr 2000 12:23:57 +0200

/etc/john.ini

/etc/john-mail.conf

/etc/john-mail.msg

#!/bin/sh -e

. /usr/share/debconf/confmodule

db_input medium john/cronjob || true

db_go

Source: john

Section: admin

Priority: optional

Maintainer: Christian Kurz <shorty@debian.org>

Origin: debian

Bugs: debbugs://bugs.debian.org

Standards-Version: 3.5.6

Package: john

Architecture: i386 alpha sparc 

Depends: ${shlibs:Depends}

Description: An active password cracking tool

 john, normally called john the ripper, is a tool to find

 weak passwords of your users, and even mail them automatically 

 if you want.

This is a Debian prepackaged version of john the ripper. The package has

been created by Christian Kurz <shorty@debian.org>.

Source code was obtained from:

		http://www.openwall.com/john/

The following copyright applies to this package:

 Copyright (c) 2000 Solar Designer <solar@false.com>.

 All rights reserved.

 This program is free software; you can redistribute it and/or modify it

 under the terms of the GNU General Public License as published by the Free

 Software Foundation; either version 2 of the License, or (at your option)

 any later version.

 This program is distributed in the hope that it will be useful, but WITHOUT

 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or

 FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for

 more details.

 You should have received a copy of the GNU General Public License along

 with this program; if not, write to the Free Software Foundation, Inc.,

 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.

 A complete version of the  GPL can be found in /usr/share/common-licenses/GPL.

#!/bin/bash -e

if [ -d /proc ]; then

	if grep -q '^flags.* mmx' /proc/cpuinfo; then

		exec -a john /usr/sbin/john-mmx $*

	else

		exec -a john /usr/sbin/john-any $*

	fi

else

	echo "Proc File System not available. Can't run john."

fi

exit 0

#!/bin/sh

usage() {

    echo "Usage: john-cronjob [ install | remove ]"

}

if [ $# -ne 1 ];then

    usage

    exit 0

fi

case "$1" in

    remove)

        if [ -f /etc/cron.daily/john -a ! -L /etc/cron.daily/john ]; then

            rm /etc/cron.daily/john

        fi

        ;;

    install)

        if [ ! -e /etc/cron.daily/john -a ! -L /etc/cron.daily/john ]; then

            cp /usr/share/john/john-dailyscript /etc/cron.daily/john

            chmod u+x,og-rwx  /etc/cron.daily/john

        fi

        ;;

    *)

        usage

        exit 0

        ;;

esac

\"                                      Hey, EMACS: -*- nroff -*-

\"

.\" john.1 is copyright 1999-2001 by

.\" Jeronimo Pellegrini <pellegrini@mpcnet.com.br>

.\" This is free documentation, see the latest version of the GNU General

.\" Public License for copying conditions. There is NO warranty.

.TH JOHN-CRONJOB 1 "August 21, 2001" john

.\" Please adjust this date whenever revising the manpage.

.SH NAME

john-cronjob \- installs or removes the john cronjob

.SH SYNOPSIS

.B john-cronjob

install | remove

.SH DESCRIPTION

This manual page describes the john-cronjob script, an add-on to the john

package. \fBjohn-cronjob\fP is used to install or remove a cronjob that will

run automatically every day, trying to crack passwords (a script will be

placed

under \fI/etc/cron.daily\fP). When the script is called, it will check if an

instance of john is already running. If not, it will start a new \fBjohn\fP(1)

process, and then run the \fBmailer\fP(1) script.

.br

When installing or removing the cronjob, this script will never touch a 

symlink.

.SH SEE ALSO

.BR mailer (1),

.BR john (1),

.BR unafs (1),

.BR unique (1),

.BR unshadow (1),

.BR john.ini (5)

.PP

The programs are documented fully by John's documentation,

which should be available in \fI/usr/share/doc/john\fP or other

location, depending on your system.

.SH AUTHOR

This manual page was written by Jeronimo  Pellegrini

<pellegrini@mpcnet.com.br>, for the Debian GNU/Linux system (but 

may be used by others).

.br

John the Ripper was written by Solar Designer <solar@openwall.com>.

The complete list of contributors can be found in the CREDITS file

in the documentation directory.

#!/bin/sh

#

# This script runs every day, trying to crack passwords, and then calls

# mailer to warn the users (and maybe also root) about that.

JOHNDIR=/usr/sbin

PASSWD=/etc/passwd

SHADOW=/etc/shadow

PASSFILE=`grep -e "[ ]*passfile[ ]*=[ ]*" /etc/john-mail.conf |

          sed -e "s/#.*//" -e "s/.*=[ ]*//"`

if [ -z $PASSFILE ]; then

       mail -s "John cronjob is not configured yet!" root <<EOF

John was set up to run every day, but it needs you to specify a

temporary file, with a "passfile=" line in /etc/john-mail.conf.

Thank you,

John the Ripper, an automated password cracking tool.

EOF

       exit 0

fi

TMPFILE=`mktemp $PASSFILE.XXXXXX` || exit 1

chmod og-rwx $TMPFILE

if [ -f $SHADOW ]; then

       $JOHNDIR/unshadow $PASSWD $SHADOW >> $TMPFILE

else

       cat $PASSWD >> $TMPFILE

fi

if [ ! -f /var/lock/john ]; then

       touch /var/lock/john

       $JOHNDIR/john -single $TMPFILE

       rm -f /var/lock/john

       $JOHNDIR/mailer $TMPFILE

       rm -f $TMPFILE

else

       mail -s "John is running" root <<EOF

John is running at $HOSTNAME -- either the cronjob lasted too long,

or someone else is running john.

EOF

fi

# Sample configuration file for john.

#

# These are the shells that should be ignored by john. If you

# install falselogin, for example, you may want to add it to

# the list.

shells=-,/bin/false,/dev/null,/bin/sync

# This is the mail command. You may actually use any program

# here; the message in /etc/john.msg will be piped into it,

# with the login name and host name substituted.

# You may want to use a program to log information about

# weak passwords (but that means sensitive information would be

# kept somewhere - be careful!)

mailcmd=/usr/sbin/sendmail

# This is the passfile, which defines a temporary file that contains

# the content of /etc/passwd and /etc/shadow while the cronjob is run.

# Since this file contains sensible data, no default is provided and

# you need to specify a file name to be used."

# passfile=

Subject: Bad password!

Hello!

Your password for account @LOGIN at host @HOSTNAME is too easy!

Please change it as soon as possible.

John the Ripper, an automated password cracker.

.\"                                      Hey, EMACS: -*- nroff -*-

.\"

.\" john.1 is copyright 1999-2001 by

.\" Jordi Mallach <jordi@debian.org>

.\" This is free documentation, see the latest version of the GNU General

.\" Public License for copying conditions. There is NO warranty.

.TH JOHN 1 "June 25, 2001" john

.\" Please adjust this date whenever revising the manpage.

.SH NAME

john \- a tool to find weak passwords of your users

.SH SYNOPSIS

.B john

.RI [ options ] " password-files"

.SH DESCRIPTION

This manual page documents briefly the

.B john

command.

This manual page was written for the Debian GNU/Linux distribution

because the original program does not have a manual page.

\fBjohn\fP, better known as John the Ripper, is a tool to find weak

passwords of users in a server. John can use a dictionary or some search

pattern as well as a password file to check for passwords. John supports

different cracking modes and understands many ciphertext formats, like

several DES variants, MD5 and blowfish. It can also be used to extract AFS

and Windows NT passwords.

.SH USAGE

To use John, you just need to supply it a password file and the desired

options. If no mode is specified, john will try "single" first, then

"wordlist" and finally "incremental".

.P

Once John finds a password, it will be printed to the terminal and saved

into a file called ~/john.pot. John will read this file when it restarts

so it doesn't try to crack already done passwords.

.P

To see the cracked passwords, use

.P

john -show passwd

.P

While cracking, you can press any key for status, or Ctrl+C to abort the

session, saving point information to a file (

.I ~/restore

by default). By the

way, if you press Ctrl+C twice John will abort immediately without saving.

The point information is also saved every 10 minutes (configurable in the

configuration file,

.I ~/john.ini

) in case of a crash.

.P

To continue an interrupted session, run:

.P

john -restore

.P

Now, you may notice that many accounts have a disabled shell, you can make

John ignore these (assume that shell is called '

.I /etc/expired

'):

.P

john -show -shells:-/etc/expired passwd

.P

You might want to mail all the users who got weak passwords,

to tell them to change the passwords. It's not always a good idea though

(unfortunately, lots of people seem to ignore such mail, it can be used

as a hint for crackers, etc), but anyway, I'll assume you know what you're

doing. Get a copy of the 'mailer' script supplied with John, so you won't

change anything that's under

.I /usr/bin

; edit the message it sends, and

possibly the mail command inside it (especially if the password file is

from a different box than you got John running on).

Then run:

.P

 ./mailer passwd

.P

Anyway, you probably should have a look at

.I /usr/share/doc/john/OPTIONS

for a list of all the command line options, and at

.I /usr/share/doc/john/EXAMPLES

for more John usage examples with other cracking modes.

.SH OPTIONS

All the options recognized by john start with a single dash (`-').

A summary of options is included below.

.TP

.B \-external:MODE

Enables an external mode, using external functions defined in ~/john.ini's

[List.External:MODE] section.

.TP

.B \-format:NAME

Allows you to override the ciphertext format detection. Currently, valid

format names are DES, BSDI, MD5, BF, AFS, LM. You can use this option when

cracking or with '-test'. Note that John can't crack password files with

different ciphertext formats at the same time.

.TP

.B \-groups:[-]GID[,..]

Tells John to load users of the specified group(s) only.

.TP

.B \-incremental[:MODE]

Enables the incremental mode, using the specified ~/john.ini definition

(section [Incremental:MODE], or [Incremental:All] by default).

.TP

.B \-makechars:FILE

Generates a charset file, based on character frequencies from ~/john.pot,

for use with the incremental mode. The entire ~/john.pot will be used for

the charset file unless you specify some password files. You can also use

an external filter() routine with this option.

.TP

.B \-restore[:FILE]

Continues an interrupted cracking session, reading point information from

the specified file (~/restore by default).

.TP

.B \-rules

Enables wordlist rules, that are read from [List.Rules:Wordlist].

.TP

.B \-salts:[-]COUNT

This feature sometimes allows to achieve better performance. For example

you can crack only some salts using '-salts:2' faster, and then crack the

rest using '-salts:-2'. Total cracking time will be about the same, but

you will get some passwords cracked earlier.

.TP

.B \-savemem:LEVEL

You might need this option if you don't have enough memory, or don't want

John to affect other processes too much. Level 1 tells John not to waste

memory on login names, so you won't see them while cracking. Higher levels

have a performance impact: you should probably avoid using them unless John

doesn't work or gets into swap otherwise.

.TP

.B \-session:FILE

Allows you to specify another point information file's name to use for

this cracking session. This is useful for running multiple instances of

John in parallel, or just to be able to recover an older session later,

not always continue the latest one.

.TP

.B \-shells:[-]SHELL[,..]

This option is useful to load accounts with a valid shell only, or not to

load accounts with a bad shell. You can omit the path before a shell name,

so '-shells:csh' will match both '/bin/csh' and '/usr/bin/csh', while

'-shells:/bin/csh' will only match '/bin/csh'.

.TP

.B \-show

Shows the cracked passwords in a convenient form. You should also specify

the password files. You can use this option while another John is cracking,

to see what it did so far.

.TP

.B \-single

Enables the "single crack" mode, using rules from [List.Rules:Single].

.TP

.B \-status[:FILE]

Prints status of an interrupted or running session. To get an up to date

status information of a detached running session, send that copy of John

a SIGHUP before using this option.

.TP

.B \-stdin

These are used to enable the wordlist mode (reading from stdin).

.TP

.B \-stdout[:LENGTH]

When used with a cracking mode, except for "single crack", makes John

print the words it generates to stdout instead of cracking. While applying

wordlist rules, the significant password length is assumed to be LENGTH,

or unlimited by default.

.TP

.B \-test

Benchmarks all the enabled ciphertext format crackers, and tests them for

correct operation at the same time.

.TP

.B \-users:[-]LOGIN|UID[,..]

Allows you to filter a few accounts for cracking, etc. A dash before the

list can be used to invert the check (that is, load all the users that

aren't listed).

.TP

.B \-wordfile:FILE

These are used to enable the wordlist mode, reading words from FILE.

.SH MODES

John can work in the following modes:

.TP

\fBWordlist\fP

John will simply use a file with a list of words that will be checked

against the passwords. See RULES for the format of wordlist files.

.TP

\fBSingle crack\fP

In this mode, john will try to crack the password using the login/GECOS

information as passwords.

.TP

\fBIncremental\fP

This is the most powerful mode. John will try any character combination

to resolve the password.

Details about these modes can be found in the MODES file in john's

documentation, including how to define your own cracking methods.

.SH SEE ALSO

.BR mailer (1),

.BR unafs (1),

.BR unique (1),

.BR unshadow (1),

.BR john.ini (5)

.PP

The programs are documented fully by John's documentation,

which should be available in \fI/usr/share/doc/john\fP or other

location, depending on your system.

.SH AUTHOR

This manual page was written by Jordi Mallach <jordi@debian.org>

and Jeronimo  Pellegrini <pellegrini@mpcnet.com.br>, for the

Debian GNU/Linux system (but may be used by others).

.br

John the Ripper was written by Solar Designer <solar@openwall.com>.

The complete list of contributors can be found in the CREDITS file

in the documentation directory.

#!/bin/sh

#

# This file is part of John the Ripper password cracker,

# Copyright (c) 1996-98 by Solar Designer

#

if [ $# -ne 1 ]; then

	echo "Usage: $0 PASSWORD-FILE"

	exit 0

fi

if [ ! -f /etc/john-mail.conf ]; then

       echo "Couldn't find /etc/john-mail.conf -- stopping!"

       exit 0

fi

if [ ! -f /etc/john-mail.msg ]; then

        echo "Couldn't find /etc/john-mail.msg -- stopping!"

        exit 0

fi

# In Debian, john should be in /usr/sbin. "john" binaries in other

# locations should not be used.

JOHNDIR=/usr/sbin

# Let's get stuff from conf file:

SHELLS=`grep   -e "shells[ ]*=[ ]*"  /etc/john-mail.conf | sed "s/.*=[ ]*//"`

MAILCMD=`grep  -e "mailcmd[ ]*=[ ]*" /etc/john-mail.conf | sed "s/.*=[ ]*//"`

MAILARGS=`grep -e "mailargs[ ]*=[ ]*" /etc/john-mail.conf | sed "s/.*=[ ]*//"`

# Let's start

$JOHNDIR/john -show "$1" -shells:$SHELLS | sed -n 's/:.*//p' |

(

	SENT=0

	while read LOGIN; do

		echo Sending mail to "$LOGIN"...

# Sends a message to each user; a template is in /etc/john.msg

# Subject, Reply-to, and other header lines should be put

# at the top of that file.

        sed -e 's/@LOGIN/'$LOGIN'/g' \

            -e 's/@HOSTNAME/'$HOSTNAME'/g' /etc/john-mail.msg |

        $MAILCMD $MAILARGS $LOGIN

		SENT=$(($SENT+1))

	done

	echo $SENT messages sent

)

.\"                                      Hey, EMACS: -*- nroff -*-

.\"

.\" mailer.1 is copyright 1999-2001 by

.\" Jordi Mallach <jordi@debian.org>

.\" This is free documentation, see the latest version of the GNU General

.\" Public License for copying conditions. There is NO warranty.

.TH MAILER 1 "May 19, 2001" john

.\" Please adjust this date whenever revising the manpage.

.SH NAME

mailer \- script to warn users about their week passwords

.SH SYNOPSIS

.B mailer

\fIpassword-files\fP

.SH DESCRIPTION

This manual page documents briefly the

.B mailer

command, which is part of the john package.

This manual page was written for the Debian GNU/Linux distribution

because the original program does not have a manual page.

\fBjohn\fP, better known as John the Ripper, is a tool to find weak

passwords of users in a server.

.br

The \fBmailer\fP tool is useful to inform users which have been found to

be using weak passwords by mail.

.P

You should edit the message mailer will send to the users, but remember to

copy the script to a safe place before editing it, as it's

generally a bad idea to modify things living in /usr.

.SH SEE ALSO

.BR john (1),

.BR unafs (1),

.BR unique (1),

.BR unshadow (1),

.BR john.ini (5)

.PP

The programs are documented fully by John's documentation,

which should be available in \fI/usr/share/doc/john\fP or other

location, depending on your system.

.SH AUTHOR

This manual page was written by Jordi Mallach <jordi@debian.org>,

for the Debian GNU/Linux system (but may be used by others).

.br

John the Ripper and mailer were written by Solar Designer

<solar@openwall.com>. The complete list of contributors can be found in

the CREDITS file in the documentation directory.

john: interpreter-not-absolute ./usr/share/john/password.lst #!comment:

john: script-not-executable ./usr/share/john/password.lst

john: unusual-interpreter ./usr/share/john/password.lst #!comment:

john: missing-debconf-dependency

#!/bin/sh -e

if [ "$1" = "configure" ]; then

        if [ -d /usr/doc -a ! -e /usr/doc/john -a -d /usr/share/doc/john ]; then

                ln -sf ../share/doc/john /usr/doc/john

        fi

fi

if [ -f /usr/share/debconf/confmodule ]; then

	. /usr/share/debconf/confmodule

	db_get john/cronjob ; INSTCRON="$RET"

	if [ "$INSTCRON" = "true" ]; then

		john-cronjob install

	else

		john-cronjob remove

	fi

else

	cat <<%END%

 I can install a cronjob for you that will run periodically, trying

 to crack passwords, and then mail users with weak passwords.

 You will have to configure the path and name of the temporary

 file in /etc/john-mailer.conf.

 .

 If you decide not to install now, you can always run

 "john.cron install" to install it if you change your mind.

Should I install the cronjob?

%END%

	read a

	case "$a" in

		[yY]*)

			john-cronjob install

			;;

		[nN]*)

			john-cronjob remove

	esac

fi

#!/bin/sh

if [ "$1" = purge -a -e /usr/share/debconf/confmodule ]; then

        . /usr/share/debconf/confmodule

        db_purge

fi

#!/bin/sh

# Remove runtime file when purging john.

[ "$1" = "remove" ] && rm -f /usr/share/john/restore

if [ \( "$1" = "upgrade" -o "$1" = "remove" \) -a -L /usr/doc/john ]; then

	rm -f /usr/doc/john

fi

# Check if a cronjob was installed and if yes, remove it.

if [ -f /etc/cron.daily/john ]; then

	/usr/sbin/john-cronjob remove

fi

#!/usr/bin/make -f

PACKAGE := john

TARGET:=$(shell dpkg --print-architecture | sed 's/i386/linux-x86-any-elf/;s/alpha/linux-alpha/;s/sparc/linux-sparc/')

ARCHITECURE:=$(shell dpkg --print-architecture)

build: build-stamp

build-stamp:

		test -e debian/control

ifeq ($(ARCHITECURE),i386)

			cd $(CURDIR)/src && make $(TARGET)

			mv run/john run/john-any

			cd $(CURDIR)/src && make clean

			cd $(CURDIR)/src && make linux-x86-mmx-elf

			mv run/john run/john-mmx

else	

		cd $(CURDIR)/src && make $(TARGET)

endif

		touch build-stamp

clean:

		test -e debian/control

		test 0 = "`id -u`" || (echo need root privileges; exit 1)

		rm -f build-stamp install-stamp

		-$(MAKE) clean

		rm -rf debian/substvars debian/files debian/tmp

# Build architecture-independent files here.

binary-indep: build

# We have nothing to do by default.

# Build architecture-dependent files here.

binary-arch: build debian/control

		test -e debian/control

		test 0 = "`id -u`" || (echo need root privileges; exit 1)

		rm -rf debian/substvars debian/tmp

		install -d --mode=0755 debian/tmp

		install -d --mode=0755 "debian/tmp/usr/share/doc/$(PACKAGE)"

		install -d --mode=0755 "debian/tmp/usr/share/man/man1"

		install -d --mode=0755 "debian/tmp/usr/share/lintian/overrides"

		install -d --mode=0755 "debian/tmp/usr/share/$(PACKAGE)"

		install -d --mode=0755 "debian/tmp/usr/sbin"

		install -d --mode=0755 "debian/tmp/etc"

		install -m 644 run/john.ini debian/tmp/etc

		install -m 644 run/all.chr debian/tmp/usr/share/john

		install -m 644 run/alpha.chr debian/tmp/usr/share/john

		install -m 644 run/digits.chr debian/tmp/usr/share/john

		install -m 644 run/lanman.chr debian/tmp/usr/share/john

		install -m 644 run/password.lst debian/tmp/usr/share/john

		# Extra Stuff that should be removed after the next

		# upstream release of john the ripper

		install -m 644 debian/john-mail.msg debian/tmp/etc

		install -m 644 debian/john-mail.conf debian/tmp/etc

		install -m 644 debian/CONFIG.mailer debian/tmp/usr/share/doc/$(PACKAGE)

		install -m 755 debian/mailer debian/tmp/usr/sbin

		install -m 755 debian/john-cronjob debian/tmp/usr/sbin

		install -m 755 debian/john-dailyscript debian/tmp/usr/share/$(PACKAGE)

ifeq (i386,$(ARCHITECURE))

		install -s run/john-any debian/tmp/usr/sbin/john-any

		install -s run/john-mmx debian/tmp/usr/sbin/john-mmx

		install -m 755 debian/john debian/tmp/usr/sbin/john

else

		install -s run/john debian/tmp/usr/sbin/john

endif

		#Commented out, because currently we'll use a special

		#hacked version. Comment it in after new upstream release.

		#install run/mailer debian/tmp/usr/sbin

ifeq (i386,$(ARCHITECURE))

		(cd debian/tmp/usr/sbin; ln -s john-any unafs; ln -s john-any unique; \

		ln -s john-any unshadow)

else

		(cd debian/tmp/usr/sbin; ln -s john unafs; ln -s john unique; \

		ln -s john unshadow)

endif

		install --mode=0644 debian/overrides.Lintian \

			debian/tmp/usr/share/lintian/overrides/john

		install --mode=0644 debian/copyright \

			"debian/tmp/usr/share/doc/$(PACKAGE)"

		install --mode=0644 doc/CONFIG doc/CREDITS doc/EXAMPLES doc/EXTERNAL doc/README \

		   "debian/tmp/usr/share/doc/$(PACKAGE)"

		install --mode=0644 doc/FAQ doc/MODES doc/OPTIONS doc/RULES doc/NEWS \

		   "debian/tmp/usr/share/doc/$(PACKAGE)"

		install --mode=0644 debian/changelog \

			"debian/tmp/usr/share/doc/$(PACKAGE)/changelog.Debian"

		mv debian/tmp/usr/share/doc/$(PACKAGE)/NEWS \

		   debian/tmp/usr/share/doc/$(PACKAGE)/changelog

		install --mode=0644 debian/john.1 "debian/tmp/usr/share/man/man1"

		install --mode=0644 debian/mailer.1 "debian/tmp/usr/share/man/man1"

		install --mode=0644 debian/unafs.1 "debian/tmp/usr/share/man/man1"

		install --mode=0644 debian/unique.1 "debian/tmp/usr/share/man/man1"

		install --mode=0644 debian/unshadow.1 "debian/tmp/usr/share/man/man1"

		install --mode=0644 debian/john-cronjob.1 "debian/tmp/usr/share/man/man1"

		gzip -9 debian/tmp/usr/share/doc/$(PACKAGE)/changelog

		gzip -9 debian/tmp/usr/share/doc/$(PACKAGE)/changelog.Debian

		gzip -9 debian/tmp/usr/share/doc/$(PACKAGE)/EXAMPLES

		gzip -9 debian/tmp/usr/share/man/man1/john.1

		gzip -9 debian/tmp/usr/share/man/man1/mailer.1

		gzip -9 debian/tmp/usr/share/man/man1/unafs.1

		gzip -9 debian/tmp/usr/share/man/man1/unique.1

		gzip -9 debian/tmp/usr/share/man/man1/unshadow.1

		gzip -9 debian/tmp/usr/share/man/man1/john-cronjob.1

ifeq (i386,$(ARCHITECURE))

		strip --remove-section=.comment --remove-section=.note debian/tmp/usr/sbin/john-any

		strip --remove-section=.comment --remove-section=.note debian/tmp/usr/sbin/john-mmx

else

		strip --remove-section=.comment --remove-section=.note debian/tmp/usr/sbin/john

endif

		install -d --mode=0755 debian/tmp/DEBIAN

		install --mode=0755 debian/prerm debian/postinst debian/tmp/DEBIAN

		install --mode=0644 debian/conffiles debian/tmp/DEBIAN

		install --mode=0755 debian/config debian/tmp/DEBIAN

		install --mode=0644 debian/templates debian/tmp/DEBIAN

		install --mode=0755 debian/postinst debian/tmp/DEBIAN

		dpkg-shlibdeps debian/tmp/usr/sbin/*

		dpkg-gencontrol -isp

		dpkg --build debian/tmp ..

source diff:

		@echo >&2 'source and diff are obsolete - use dpkg-source -b'; false

binary: binary-indep binary-arch

.PHONY: build clean binary-indep binary-arch binary

Template: john/cronjob

Type: boolean

Default: false

Description: Should John run periodically and mail users?

 I can install a cronjob for you that will run periodically, trying

 to crack passwords, and then mail users with weak passwords.

 You will have to configure the path and name of the temporary

 file in /etc/john-mail.conf.

 .

 If you decide not to install now, you can always run

 "john.cron install" to install it if you change your mind.

 Should I install the cronjob?

Description-de: John regelmäßig ausführen und Nutzer anmailen?

 Es kann ein Cron-Job installiert werden, der John regelmäßig ausführt,

 und versucht Passwörter zu knacken. Nutzer mit zu einfachen Passwörtern

 werden dann per eMail darüber informiert. Sie müsssen dazu den Pfad und

 Namen einer temporären Datei in /etc/john-mail.conf angeben.

 .

 Wenn Sie dies jetzt nicht tun möchten, dann können Sie jederzeit

 "john.cron install" ausführen, um den Cron-Job nachträglich zu

 installieren

.\"                                      Hey, EMACS: -*- nroff -*-

.\"

.\" unafs.1 is copyright 1999-2001 by

.\" Jordi Mallach <jordi@debian.org>

.\" This is free documentation, see the latest version of the GNU General

.\" Public License for copying conditions. There is NO warranty.

.TH UNAFS 1 "May 19, 2001" john

.\" Please adjust this date whenever revising the manpage.

.SH NAME

unafs \- script to warn users about their week passwords

.SH SYNOPSIS

.B unafs

\fIpassword-files cell-name\fP

.SH DESCRIPTION

This manual page documents briefly the

.B unafs

command, which is part of the john package.

This manual page was written for the Debian GNU/Linux distribution

because the original program does not have a manual page.

\fBjohn\fP, better known as John the Ripper, is a tool to find weak

passwords of users in a server.

.br The \fBunafs\fP tool gets password hashes out of the binary AFS

database, and produces a file usable by John.

.SH SEE ALSO

.BR john (1),

.BR mailer (1),

.BR unique (1),

.BR unshadow (1),

.BR john.ini (5)

.PP

The programs are documented fully by John's documentation,

which should be available in \fI/usr/share/doc/john\fP or other

location, depending on your system.

.SH AUTHOR

This manual page was written by Jordi Mallach <jordi@debian.org>,

for the Debian GNU/Linux system (but may be used by others).

.br

John the Ripper and mailer were written by Solar Designer

<solar@openwall.com>. The complete list of contributors can be found in

the CREDITS file in the documentation directory.

.\"                                      Hey, EMACS: -*- nroff -*-

.\"

.\" unique.1 is copyright 1999-2001 by

.\" Jordi Mallach <jordi@debian.org>

.\" This is free documentation, see the latest version of the GNU General

.\" Public License for copying conditions. There is NO warranty.

.TH UNIQUE 1 "May 19, 2001" john

.\" Please adjust this date whenever revising the manpage.

.SH NAME

unique \- removes duplicates from a wordlist

.SH SYNOPSIS

.B unique

\fIoutput-file\fP

.SH DESCRIPTION

This manual page documents briefly the

.B unique

command, which is part of the john package.

This manual page was written for the Debian GNU/Linux distribution

because the original program does not have a manual page.

\fBjohn\fP, better known as John the Ripper, is a tool to find weak

passwords of users in a server.

.br The \fBunique\fP tool finds and removes duplicate entries from a

wordlist (read from stdin), without changing the order. This is important

to increase the performance of john when using the wordlist method.

.SH SEE ALSO

.BR john (1),

.BR mailer (1),

.BR unafs (1),

.BR unshadow (1),

.BR john.ini (5)

.PP

The programs are documented fully by John's documentation,

which should be available in \fI/usr/share/doc/john\fP or other

location, depending on your system.

.SH AUTHOR

This manual page was written by Jordi Mallach <jordi@debian.org>,

for the Debian GNU/Linux system (but may be used by others).

.br

John the Ripper and mailer were written by Solar Designer

<solar@openwall.com>. The complete list of contributors can be found in

the CREDITS file in the documentation directory.

.\"                                      Hey, EMACS: -*- nroff -*-

.\"

.\" unshadow.1 is copyright 1999-2001 by

.\" Jordi Mallach <jordi@debian.org>

.\" This is free documentation, see the latest version of the GNU General

.\" Public License for copying conditions. There is NO warranty.

.TH UNSHADOW 1 "May 19, 2001" john

.\" Please adjust this date whenever revising the manpage.

.SH NAME

unshadow \- combines passwd and shadow files

.SH SYNOPSIS

.B unshadow

\fIpassword-file shadow-file\fP

.SH DESCRIPTION

This manual page documents briefly the

.B unshadow

command, which is part of the john package.

This manual page was written for the Debian GNU/Linux distribution

because the original program does not have a manual page.

\fBjohn\fP, better known as John the Ripper, is a tool to find weak

passwords of users in a server.

.br The \fBunshadow\fP tool combines the passwd and shadow files so John can

use them. You might need this since if you only used your shadow file, the

GECOS information wouldn't be used by the "single crack" mode, and also you

wouldn't be able to use the '-shells' option. On a normal system you'll need

to run unshadow as root to be able to read the shadow file.

.SH SEE ALSO

.BR john (1),

.BR mailer (1),

.BR unafs (1),

.BR unique (1),

.BR john.ini (5)

.PP

The programs are documented fully by John's documentation,

which should be available in \fI/usr/share/doc/john\fP or other

location, depending on your system.

.SH AUTHOR

This manual page was written by Jordi Mallach <jordi@debian.org>,

for the Debian GNU/Linux system (but may be used by others).

.br

John the Ripper and mailer were written by Solar Designer

<solar@openwall.com>. The complete list of contributors can be found in

the CREDITS file in the documentation directory.

		    GNU GENERAL PUBLIC LICENSE

		       Version 2, June 1991

 Copyright (C) 1989, 1991 Free Software Foundation, Inc.

                       59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

 Everyone is permitted to copy and distribute verbatim copies

 of this license document, but changing it is not allowed.

			    Preamble

  The licenses for most software are designed to take away your

freedom to share and change it.  By contrast, the GNU General Public

License is intended to guarantee your freedom to share and change free

software--to make sure the software is free for all its users.  This

General Public License applies to most of the Free Software

Foundation's software and to any other program whose authors commit to

using it.  (Some other Free Software Foundation software is covered by

the GNU Library General Public License instead.)  You can apply it to

your programs, too.

  When we speak of free software, we are referring to freedom, not

price.  Our General Public Licenses are designed to make sure that you

have the freedom to distribute copies of free software (and charge for

this service if you wish), that you receive source code or can get it

if you want it, that you can change the software or use pieces of it

in new free programs; and that you know you can do these things.

  To protect your rights, we need to make restrictions that forbid

anyone to deny you these rights or to ask you to surrender the rights.

These restrictions translate to certain responsibilities for you if you

distribute copies of the software, or if you modify it.

  For example, if you distribute copies of such a program, whether

gratis or for a fee, you must give the recipients all the rights that

you have.  You must make sure that they, too, receive or can get the

source code.  And you must show them these terms so they know their

rights.

  We protect your rights with two steps: (1) copyright the software, and

(2) offer you this license which gives you legal permission to copy,

distribute and/or modify the software.

  Also, for each author's protection and ours, we want to make certain

that everyone understands that there is no warranty for this free

software.  If the software is modified by someone else and passed on, we

want its recipients to know that what they have is not the original, so

that any problems introduced by others will not reflect on the original

authors' reputations.

  Finally, any free program is threatened constantly by software

patents.  We wish to avoid the danger that redistributors of a free

program will individually obtain patent licenses, in effect making the

program proprietary.  To prevent this, we have made it clear that any

patent must be licensed for everyone's free use or not licensed at all.

  The precise terms and conditions for copying, distribution and

modification follow.

		    GNU GENERAL PUBLIC LICENSE

   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. This License applies to any program or other work which contains

a notice placed by the copyright holder saying it may be distributed

under the terms of this General Public License.  The "Program", below,

refers to any such program or work, and a "work based on the Program"

means either the Program or any derivative work under copyright law:

that is to say, a work containing the Program or a portion of it,

either verbatim or with modifications and/or translated into another

language.  (Hereinafter, translation is included without limitation in

the term "modification".)  Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not

covered by this License; they are outside its scope.  The act of

running the Program is not restricted, and the output from the Program

is covered only if its contents constitute a work based on the

Program (independent of having been made by running the Program).

Whether that is true depends on what the Program does.

  1. You may copy and distribute verbatim copies of the Program's

source code as you receive it, in any medium, provided that you

conspicuously and appropriately publish on each copy an appropriate

copyright notice and disclaimer of warranty; keep intact all the

notices that refer to this License and to the absence of any warranty;

and give any other recipients of the Program a copy of this License

along with the Program.

You may charge a fee for the physical act of transferring a copy, and

you may at your option offer warranty protection in exchange for a fee.

  2. You may modify your copy or copies of the Program or any portion

of it, thus forming a work based on the Program, and copy and

distribute such modifications or work under the terms of Section 1

above, provided that you also meet all of these conditions:

    a) You must cause the modified files to carry prominent notices

    stating that you changed the files and the date of any change.

    b) You must cause any work that you distribute or publish, that in

    whole or in part contains or is derived from the Program or any

    part thereof, to be licensed as a whole at no charge to all third

    parties under the terms of this License.

    c) If the modified program normally reads commands interactively

    when run, you must cause it, when started running for such

    interactive use in the most ordinary way, to print or display an

    announcement including an appropriate copyright notice and a

    notice that there is no warranty (or else, saying that you provide

    a warranty) and that users may redistribute the program under

    these conditions, and telling the user how to view a copy of this

    License.  (Exception: if the Program itself is interactive but

    does not normally print such an announcement, your work based on

    the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole.  If

identifiable sections of that work are not derived from the Program,

and can be reasonably considered independent and separate works in

themselves, then this License, and its terms, do not apply to those

sections when you distribute them as separate works.  But when you

distribute the same sections as part of a whole which is a work based

on the Program, the distribution of the whole must be on the terms of

this License, whose permissions for other licensees extend to the

entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest

your rights to work written entirely by you; rather, the intent is to

exercise the right to control the distribution of derivative or

collective works based on the Program.

In addition, mere aggregation of another work not based on the Program

with the Program (or with a work based on the Program) on a volume of

a storage or distribution medium does not bring the other work under

the scope of this License.

  3. You may copy and distribute the Program (or a work based on it,

under Section 2) in object code or executable form under the terms of

Sections 1 and 2 above provided that you also do one of the following:

    a) Accompany it with the complete corresponding machine-readable

    source code, which must be distributed under the terms of Sections

    1 and 2 above on a medium customarily used for software interchange; or,

    b) Accompany it with a written offer, valid for at least three

    years, to give any third party, for a charge no more than your

    cost of physically performing source distribution, a complete

    machine-readable copy of the corresponding source code, to be

    distributed under the terms of Sections 1 and 2 above on a medium

    customarily used for software interchange; or,

    c) Accompany it with the information you received as to the offer

    to distribute corresponding source code.  (This alternative is

    allowed only for noncommercial distribution and only if you

    received the program in object code or executable form with such

    an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for

making modifications to it.  For an executable work, complete source

code means all the source code for all modules it contains, plus any

associated interface definition files, plus the scripts used to

control compilation and installation of the executable.  However, as a

special exception, the source code distributed need not include

anything that is normally distributed (in either source or binary

form) with the major components (compiler, kernel, and so on) of the

operating system on which the executable runs, unless that component

itself accompanies the executable.

If distribution of executable or object code is made by offering

access to copy from a designated place, then offering equivalent

access to copy the source code from the same place counts as

distribution of the source code, even though third parties are not

compelled to copy the source along with the object code.

  4. You may not copy, modify, sublicense, or distribute the Program

except as expressly provided under this License.  Any attempt

otherwise to copy, modify, sublicense or distribute the Program is

void, and will automatically terminate your rights under this License.

However, parties who have received copies, or rights, from you under

this License will not have their licenses terminated so long as such

parties remain in full compliance.

  5. You are not required to accept this License, since you have not

signed it.  However, nothing else grants you permission to modify or

distribute the Program or its derivative works.  These actions are

prohibited by law if you do not accept this License.  Therefore, by

modifying or distributing the Program (or any work based on the

Program), you indicate your acceptance of this License to do so, and

all its terms and conditions for copying, distributing or modifying

the Program or works based on it.

  6. Each time you redistribute the Program (or any work based on the

Program), the recipient automatically receives a license from the

original licensor to copy, distribute or modify the Program subject to

these terms and conditions.  You may not impose any further

restrictions on the recipients' exercise of the rights granted herein.

You are not responsible for enforcing compliance by third parties to

this License.

  7. If, as a consequence of a court judgment or allegation of patent

infringement or for any other reason (not limited to patent issues),

conditions are imposed on you (whether by court order, agreement or

otherwise) that contradict the conditions of this License, they do not

excuse you from the conditions of this License.  If you cannot

distribute so as to satisfy simultaneously your obligations under this

License and any other pertinent obligations, then as a consequence you

may not distribute the Program at all.  For example, if a patent

license would not permit royalty-free redistribution of the Program by

all those who receive copies directly or indirectly through you, then

the only way you could satisfy both it and this License would be to

refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under

any particular circumstance, the balance of the section is intended to

apply and the section as a whole is intended to apply in other

circumstances.

It is not the purpose of this section to induce you to infringe any

patents or other property right claims or to contest validity of any

such claims; this section has the sole purpose of protecting the

integrity of the free software distribution system, which is

implemented by public license practices.  Many people have made

generous contributions to the wide range of software distributed

through that system in reliance on consistent application of that

system; it is up to the author/donor to decide if he or she is willing

to distribute software through any other system and a licensee cannot

impose that choice.

This section is intended to make thoroughly clear what is believed to

be a consequence of the rest of this License.

  8. If the distribution and/or use of the Program is restricted in

certain countries either by patents or by copyrighted interfaces, the

original copyright holder who places the Program under this License

may add an explicit geographical distribution limitation excluding

those countries, so that distribution is permitted only in or among

countries not thus excluded.  In such case, this License incorporates

the limitation as if written in the body of this License.

  9. The Free Software Foundation may publish revised and/or new versions

of the General Public License from time to time.  Such new versions will

be similar in spirit to the present version, but may differ in detail to

address new problems or concerns.

Each version is given a distinguishing version number.  If the Program

specifies a version number of this License which applies to it and "any

later version", you have the option of following the terms and conditions

either of that version or of any later version published by the Free

Software Foundation.  If the Program does not specify a version number of

this License, you may choose any version ever published by the Free Software

Foundation.

  10. If you wish to incorporate parts of the Program into other free

programs whose distribution conditions are different, write to the author

to ask for permission.  For software which is copyrighted by the Free

Software Foundation, write to the Free Software Foundation; we sometimes

make exceptions for this.  Our decision will be guided by the two goals

of preserving the free status of all derivatives of our free software and

of promoting the sharing and reuse of software generally.

			    NO WARRANTY

  11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY

FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN

OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES

PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED

OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS

TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE

PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,

REPAIR OR CORRECTION.

  12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING

WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR

REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,

INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING

OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED

TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY

YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER

PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE

POSSIBILITY OF SUCH DAMAGES.

		     END OF TERMS AND CONDITIONS

	    How to Apply These Terms to Your New Programs

  If you develop a new program, and you want it to be of the greatest

possible use to the public, the best way to achieve this is to make it

free software which everyone can redistribute and change under these terms.

  To do so, attach the following notices to the program.  It is safest

to attach them to the start of each source file to most effectively

convey the exclusion of warranty; and each file should have at least

the "copyright" line and a pointer to where the full notice is found.

    <one line to give the program's name and a brief idea of what it does.>

    Copyright (C) <year>  <name of author>

    This program is free software; you can redistribute it and/or modify

    it under the terms of the GNU General Public License as published by

    the Free Software Foundation; either version 2 of the License, or

    (at your option) any later version.

    This program is distributed in the hope that it will be useful,

    but WITHOUT ANY WARRANTY; without even the implied warranty of

    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the

    GNU General Public License for more details.

    You should have received a copy of the GNU General Public License

    along with this program; if not, write to the Free Software

    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this

when it starts in an interactive mode:

    Gnomovision version 69, Copyright (C) year name of author

    Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.

    This is free software, and you are welcome to redistribute it

    under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate

parts of the General Public License.  Of course, the commands you use may

be called something other than `show w' and `show c'; they could even be

mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your

school, if any, to sign a "copyright disclaimer" for the program, if

necessary.  Here is a sample; alter the names:

  Yoyodyne, Inc., hereby disclaims all copyright interest in the program

  `Gnomovision' (which makes passes at compilers) written by James Hacker.

  <signature of Ty Coon>, 1 April 1989

  Ty Coon, President of Vice

This General Public License does not permit incorporating your program into

proprietary programs.  If your program is a subroutine library, you may

consider it more useful to permit linking proprietary applications with the

library.  If this is what you want to do, use the GNU Library General

Public License instead of this License.

Q: What's this?

A: It's a patch to Solar Designer's "john the ripper" password cracker.

Q: What's it good for, then?

A: It enables john to crack Windows NT/2000 MD4 (case-sensitive) password hashes.

Q: Who made this?

A: This patch was thrown together on a boring Sunday by Olle Segerdahl.

   It uses Andrew Tridgell's NTLM and MD4 code stolen from samba-2.0.7 .

Q: How do I install it?

A: I assume you are able to install john from a source distribution,

   if you are not, PLEASE read john's documentation. Put the files enclosed

   in this archive in the "src" subdirectory, run 'patch < john-ntlm.diff'

   and then 'make (your-system-type-here)' ....

Q: How do I use john to crack NT password hashes?

A: Use pwdump2 or L0phtcrack to dump the password hashes into a file,

   then run 'john pwfile -format:NT' to start cracking!

Q: Didn't it used to be '-format:NTLM' ?

A: Yes, but this has changed so as not to confuse people who have trouble

   understanding the difference between LM (DES) and NT (md4) hashes.

Q: I get all kinds of compile errors!

A: This patch was made against john-1.6.31-dev, lots of stuff might have broken

   source compatibility since then... Use something closer to john-1.6.31-dev.

Q: I have a question not covered by this FAQ!

A: Make sure you have read all there is to read about john, then

   mail me at olle@nxs.se with "JOHN-NTLM" in the subject.

/*

 * This file is part of Eggdrop blowfish patch for John The Ripper.

 * Copyright (c) 2002 by Sun-Zero <sun-zero@freemail.hu>

 * This is a free software distributable under terms of the GNU GPL. 

 * See the file COPYING for details.  

 */

#include <string.h>

#include "misc.h"

#include "formats.h"

#include "common.h"

#include "blowfish.c"

#define FORMAT_LABEL			"bfegg"

#define FORMAT_NAME			"Eggdrop"

#define ALG_NAME			"blowfish"

#define BENCHMARK_COMMENT		""

#define BENCHMARK_LENGTH		-1

#define PLAINTEXT_LENGTH		31

#define CIPHERTEXT_LENGTH		33

#define BINARY_SIZE			13

#define SALT_SIZE			0

#define MIN_KEYS_PER_CRYPT		1

#define MAX_KEYS_PER_CRYPT		1

static struct fmt_tests tests[] = {

    {"+Yug.E/gQk2S0", "ajto123"},

    {"+hG/XQ18czl5.", "ablak123"},

    {"+IaISR0x4ZY/.", "szek123"},

    {"+9VMVs/L1st7/", "konyha"},

    {"+EEHgy/MBLDd0", "walkman"},

    {"+vPBrs07OTXE/", "tesztuser"},

    {NULL}

};

static char crypt_key[BINARY_SIZE];

static char saved_key[PLAINTEXT_LENGTH + 1];

static int valid(char *ciphertext) {

    if (strncmp(ciphertext, "+", 1) != 0) return 0;

    if (strlen(ciphertext) != 13) return 0;

    return 1;

}

void init() {

    blowfish_first_init();

}

static void set_key(char *key, int index) {

  strnzcpy(saved_key, key, PLAINTEXT_LENGTH+1);

}

static char *get_key(int index) {

  return saved_key;

}

static int cmp_all(void *binary, int index) {

  return !memcmp(binary, crypt_key, BINARY_SIZE);

}

static int cmp_exact(char *source, int index) {

  return 1;

}

static void set_salt(void *salt) { }

static void crypt_all(int count) {  

    blowfish_encrypt_pass(saved_key, crypt_key);

}

struct fmt_main fmt_BFEgg = {

  {

    FORMAT_LABEL,

    FORMAT_NAME,

    ALG_NAME,

    BENCHMARK_COMMENT,

    BENCHMARK_LENGTH,

    PLAINTEXT_LENGTH,

    BINARY_SIZE,

    SALT_SIZE,

    MIN_KEYS_PER_CRYPT,

    MAX_KEYS_PER_CRYPT,

    FMT_CASE | FMT_8_BIT,

    tests

  }, {

    init,

    valid,

    fmt_default_split,

    fmt_default_binary,

    fmt_default_salt,

    {

	fmt_default_binary_hash,

	fmt_default_binary_hash,

	fmt_default_binary_hash,

    },

	fmt_default_salt_hash,

	set_salt,

	set_key,

	get_key,

	// fmt_default_clear_keys,

	crypt_all, 

	{

	    fmt_default_get_hash,

	    fmt_default_get_hash,

	    fmt_default_get_hash,

	},

	    cmp_all,

	    cmp_all,

	    cmp_exact

  }

};

/*

  KRB4_fmt.c

  AFS/krb4 TGT dictionary attack module for Solar Designer's John the Ripper.

  tgtsnarf files should only contain entries for one cell/realm.

  Copyright (c) 1999 Dug Song <dugsong@monkey.org>

  All rights reserved, all wrongs reversed.

  Redistribution and use in source and binary forms, with or without

  modification, are permitted provided that the following conditions

  are met:

  1. Redistributions of source code must retain the above copyright

     notice, this list of conditions and the following disclaimer.

  2. Redistributions in binary form must reproduce the above copyright

     notice, this list of conditions and the following disclaimer in the

     documentation and/or other materials provided with the distribution.

  3. The name of author may not be used to endorse or promote products

     derived from this software without specific prior written permission.

  THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,

  INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY

  AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL

  THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,

  EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,

  PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS;

  OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,

  WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR

  OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF

  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

*/

#include <string.h>

#include <ctype.h>

#define OPENSSL_ENABLE_OLD_DES_SUPPORT

#include <des.h>

#include "arch.h"

#include "DES_std.h"

#include "KRB4_std.h"

#include "misc.h"

#include "common.h"

#include "formats.h"

#define TGT_LENGTH		16	/* 2 des_cblock's */

#define FORMAT_LABEL		"krb4"

#define FORMAT_NAME		"Kerberos v4 TGT"

#define ALGORITHM_NAME		DES_STD_ALGORITHM_NAME

#define BENCHMARK_COMMENT	""

#define BENCHMARK_LENGTH	-1

#define PLAINTEXT_LENGTH	32

#define BINARY_SIZE		0

#define SALT_SIZE		TGT_LENGTH + REALM_SZ

#define MIN_KEYS_PER_CRYPT	1

#define MAX_KEYS_PER_CRYPT	1

static struct fmt_tests krb4_tests[] = {

	{"$af$UMICH.EDU$bb46613c503ad92e649d99d038efddb2", "w00w00"},

	{"$af$UMICH.EDU$95cd4367d4828d117b745ed63b9229be", "asdfjkl;"},

	{"$af$UMICH.EDU$000084efbde96969fd54d1a2ec8c287d", "hello!"},

	{"$af$UMICH.EDU$e9660a21b280875a7ecfc68aa771e34a", "a12345"},

	{"$af$UMICH.EDU$566f2b8629b9be36680866b0e613f239", "a1b2c3"},

	{"$af$UMICH.EDU$bebcedf43f7f2aa78cf9c0639e494c92", "abcdefg12345678"},

	{"$af$ENGIN.UMICH.EDU$9ef1034301e1f1fcf1516cb65aa1cc79", "asdfjkl;"},

	{"$af$ENGIN.UMICH.EDU$02ad23a6364df67a4db473de053cacbb", "a1b2c3"},

	{"$af$ENGIN.UMICH.EDU$14d0a59a2f9e746f1a3bf02ec4fb447e", "abc123!"},

	{"$af$ENGIN.UMICH.EDU$44feffd06e68e30bc8890e253760858d", "12345"},

	{NULL}

};

static const unsigned char odd_parity[256]={

	1,  1,  2,  2,  4,  4,  7,  7,  8,  8, 11, 11, 13, 13, 14, 14,

       16, 16, 19, 19, 21, 21, 22, 22, 25, 25, 26, 26, 28, 28, 31, 31,

       32, 32, 35, 35, 37, 37, 38, 38, 41, 41, 42, 42, 44, 44, 47, 47,

       49, 49, 50, 50, 52, 52, 55, 55, 56, 56, 59, 59, 61, 61, 62, 62,

       64, 64, 67, 67, 69, 69, 70, 70, 73, 73, 74, 74, 76, 76, 79, 79,

       81, 81, 82, 82, 84, 84, 87, 87, 88, 88, 91, 91, 93, 93, 94, 94,

       97, 97, 98, 98,100,100,103,103,104,104,107,107,109,109,110,110,

      112,112,115,115,117,117,118,118,121,121,122,122,124,124,127,127,

      128,128,131,131,133,133,134,134,137,137,138,138,140,140,143,143,

      145,145,146,146,148,148,151,151,152,152,155,155,157,157,158,158,

      161,161,162,162,164,164,167,167,168,168,171,171,173,173,174,174,

      176,176,179,179,181,181,182,182,185,185,186,186,188,188,191,191,

      193,193,194,194,196,196,199,199,200,200,203,203,205,205,206,206,

      208,208,211,211,213,213,214,214,217,217,218,218,220,220,223,223,

      224,224,227,227,229,229,230,230,233,233,234,234,236,236,239,239,

      241,241,242,242,244,244,247,247,248,248,251,251,253,253,254,254

};

static struct salt_st {

	u_char			tgt[TGT_LENGTH];

	char			realm[REALM_SZ];

} *saved_salt;

static struct key_st {

	des_cblock		key;

	des_key_schedule	sched;

	char			string[PLAINTEXT_LENGTH];

} saved_key;

static int

krb4_valid(char *ciphertext)

{

	char *p, *tgt;

	if (strncmp(ciphertext, "$k4$", 4) != 0 &&

	    strncmp(ciphertext, "$af$", 4) != 0)

		return 0;

	tgt = strchr(ciphertext + 4, '$') + 1;

	for (p = tgt; p && *p != '\0'; p++)

		if (!isxdigit((int)*p)) return 0;

	if (p - tgt != TGT_LENGTH * 2)

		return 0;

	return 1;

}

static int

hex_decode(char *src, u_char *dst, int outsize)

{

	char *p, *pe;

	u_char *q, *qe, ch, cl;

	pe = src + strlen(src);

	qe = dst + outsize;

	for (p = src, q = dst; p < pe && q < qe && isxdigit((int)*p); p += 2) {

		ch = tolower(p[0]);

		cl = tolower(p[1]);

		if ((ch >= '0') && (ch <= '9')) ch -= '0';

		else if ((ch >= 'a') && (ch <= 'f')) ch -= 'a' - 10;

		else return (-1);

		if ((cl >= '0') && (cl <= '9')) cl -= '0';

		else if ((cl >= 'a') && (cl <= 'f')) cl -= 'a' - 10;

		else return (-1);

		*q++ = (ch << 4) | cl;

	}

	return (q - dst);

}

static void *

krb4_salt(char *ciphertext)

{

	static struct salt_st salt;

	char *p;

	if (strncmp(ciphertext, "$af$", 4) == 0) {

		ciphertext += 4;

		p = strchr(ciphertext, '$');

		strnzcpy(salt.realm, ciphertext, (p - ciphertext) + 1);

		ciphertext = p + 1;

	}

	else {

		salt.realm[0] = '\0';

		ciphertext += 4;

	}

	if (hex_decode(ciphertext, salt.tgt, sizeof(salt.tgt)) !=

	    sizeof(salt.tgt))

		return (NULL);

	return (&salt);

}

static void

krb4_set_salt(void *salt)

{

	saved_salt = (struct salt_st *)salt;

}

static void

krb4_set_key(char *key, int index)

{

	if (saved_salt->realm[0] != '\0')

		afs_string_to_key(key, saved_salt->realm, &saved_key.key);

	else

		des_string_to_key(key, &saved_key.key);

	strnzcpy(saved_key.string, key, sizeof(saved_key.string));

}

static char *

krb4_get_key(int index)

{

	return (saved_key.string);

}

static void

krb4_crypt_all(int count)

{

	/* XXX - NOOP */

}

static int

krb4_check_parity(des_cblock *key)

{

	int i;

	for (i = 0; i < DES_KEY_SZ; i++) {

		if ((*key)[i] != odd_parity[(*key)[i]])

			return (0);

	}

	return (1);

}

static int

krb4_cmp_all(void *binary, int count)

{

	des_cblock tmp;

	des_set_key(&saved_key.key, saved_key.sched);

	des_pcbc_encrypt((des_cblock *)saved_salt->tgt, &tmp,

	                 sizeof(des_cblock), saved_key.sched,

	                &saved_key.key, DES_DECRYPT);

	return (krb4_check_parity(&tmp));

}

static int

krb4_cmp_one(void *binary, int count)

{

	u_char text[TGT_LENGTH];

	des_pcbc_encrypt((des_cblock *)saved_salt->tgt, (des_cblock *)text,

	                 sizeof(text), saved_key.sched, &saved_key.key,

	                 DES_DECRYPT);

	return (memcmp(text + 8, "krbtgt", 6) == 0);

}

static int

krb4_cmp_exact(char *source, int index)

{

	return (1);	/* XXX - fallthrough from krb4_cmp_one() */

}

struct fmt_main fmt_KRB4 = {

	{

		FORMAT_LABEL,

		FORMAT_NAME,

		ALGORITHM_NAME,

		BENCHMARK_COMMENT,

		BENCHMARK_LENGTH,

		PLAINTEXT_LENGTH,

		BINARY_SIZE,

		SALT_SIZE,

		MIN_KEYS_PER_CRYPT,

		MAX_KEYS_PER_CRYPT,

		FMT_CASE | FMT_8_BIT,

		krb4_tests

	}, {

		fmt_default_init,

		krb4_valid,