[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 24 Aug 2009 19:25:53 +0200
From: SL <auditor@...chat.de>
To: john-users@...ts.openwall.com
Subject: Re: patching error :((
Am 2009-08-24 um 18:36 schrieb websiteaccess:
> Pllleeeeaaasse in the name of Our Lord Jesus Christ ! I need john
> 1.7.3.1 with IPB2, PHPSMD5, RAWMD5, RAW SHA1, SALT SHA1, phpass-3
> ($H$).
>
> Is someone can patch 1.7.3.1 with "Performance patch for
> 1.7.3.1-jumbo-5" , "Fast rawMD5 SSE2 patch for 1.7.3.1-all-5",
> "phpass-3 patch for 1.7.3.1-all-5", and others algorithms to get
> finally john with "IPB2, PHPSMD5, RAWMD5, RAW SHA1, SALT SHA1,
> phpass-3
> ($H$)"
>
> It will take you only > 5 minutes < to apply patches.
>
> Don't compile, I will compile here with my mac os X (10.5)
Try this:
mkdir -p /tmp/compile
cd /tmp/compile
wget -c http://www.openwall.com/john/g/john-1.7.3.1.tar.gz
wget -c http://www.openwall.com/john/contrib/john-1.7.3.1-all-5.diff.gz
wget -c http://openwall.info/wiki/_media/john/john-1.7.3.1-all-5-
phpass-3.diff.gz
wget -c http://openwall.info/wiki/_media/john/john-1.7.3.1-all-5-fast-
rawMD5-SSE2-1.diff.gz
wget -c http://openwall.info/wiki/_media/john/john-1.7.3.1-all-5-
several-performance-updates-1.diff.gz
tar xzvf john-1.7.3.1.tar.gz
cd /tmp/compile/john-1.7.3.1
zcat ../john-1.7.3.1-all-5.diff.gz | patch -p1 -Z
zcat ../john-1.7.3.1-all-5-phpass-3.diff.gz | patch -p1 -Z
zcat ../john-1.7.3.1-all-5-fast-rawMD5-SSE2-1.diff.gz | patch -p1 -Z
zcat ../john-1.7.3.1-all-5-several-performance-updates-1.diff.gz |
patch -p1 -Z
cd /tmp/compile/john-1.7.3.1/src
make clean macosx-x86-sse2
cd ../run
./john --test --format=raw-MD5
./john --test --format=phpass-MD5
./john --test --format=raw-sha1
./john --test --format=IPB2
./john --test --format=phps
Bon courage! :-)
I am running "make clean macosx-ppc32-altivec" on my G4 instead, of
course.
My results are:
Benchmarking: Raw MD5 [raw-md5 64x1]... DONE
Raw: 919424 c/s real, 1021K c/s virtual
Benchmarking: PHPass MD5 [phpass-md5]... DONE
Raw: 373 c/s real, 427 c/s virtual
Benchmarking: Raw SHA-1 [raw-sha1]... DONE
Raw: 436802 c/s real, 485335 c/s virtual
Benchmarking: IPB2 MD5 [Invision Power Board 2.x salted MD5]... DONE
Many salts: 403788 c/s real, 476915 c/s virtual
Only one salt: 263373 c/s real, 289420 c/s virtual
Benchmarking: PHPS MD5 [MD5(MD5($pass).$salt)]... DONE
Many salts: 692742 c/s real, 799318 c/s virtual
Only one salt: 341478 c/s real, 382252 c/s virtual
I got a few warnings during compilation:
phpassMD5_fmt.c: In function 'phpassmd5_set_key':
phpassMD5_fmt.c:218: warning: pointer targets in passing argument 1
of 'strcpy' differ in signedness
phpassMD5_fmt.c: In function 'phpassmd5_get_key':
phpassMD5_fmt.c:226: warning: pointer targets in passing argument 1
of 'strcpy' differ in signedness
phpassMD5_fmt.c:226: warning: pointer targets in passing argument 2
of 'strcpy' differ in signedness
phpassMD5_fmt.c: In function 'phpassmd5_crypt_all':
phpassMD5_fmt.c:355: warning: pointer targets in passing argument 2
of 'strcpy' differ in signedness
single.c: In function 'single_init':
single.c:103: warning: passing argument 1 of 'status_init' from
incompatible pointer type
wordlist.c: In function 'do_wordlist_crack':
wordlist.c:218: warning: format '%d' expects type 'int', but argument
3 has type 'long unsigned int'
wordlist.c:219: warning: format '%d' expects type 'int', but argument
3 has type 'long unsigned int'
ppc-alti.c: In function 'DES_bs_crypt':
ppc-alti.c:79: warning: 'zero' is used uninitialized in this function
ppc-alti.c: In function 'DES_bs_crypt_25':
ppc-alti.c:182: warning: 'zero' is used uninitialized in this function
ppc-alti.c: In function 'DES_bs_crypt_LM':
ppc-alti.c:284: warning: 'zero' is used uninitialized in this function
.. but no errors, and john "works".
--
To unsubscribe, e-mail john-users-unsubscribe@...ts.openwall.com and reply
to the automated confirmation request that will be sent to you.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
