[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP19820C91B0D813ECDA7ACA7FD500@phx.gbl>
Date: Thu, 1 Aug 2013 21:55:24 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Bleeding: 4 out of 346 formats failing (linux-x86-64-native OMP build
on Intel i7)
Latest bleeding:
for f in `./john --list=format-details |cut -f 1`; do
./john --test --format=$f
done
These formats fail:
dynamic_87 [sha512(sha512($s).sha512($p)) 64/64 6144x1 sha2-OpenSSL]...
(8xOMP) FAILED (get_hash[0](28))
dynamic_1014 [md5($p.$s) (long salt) 128/128 AVX 480x4x3]... (8xOMP)
FAILED (get_hash[0](1))
eCryptfs [65536x SHA-512]... (8xOMP) FAILED (get_hash[0](1))
If I just run ./john --test (or ./john --test=0) without specifying a
format, sometimes, this format fails in addition to the other 3 formats:
dynamic_107 [WHIRLPOOL(WHIRLPOOL($s).WHIRLPOOL($p)) 64/64 6144x1
OpenSSL]... (8xOMP) FAILED (get_hash[0](2))
Sometimes I also get a core dump (instead of just a failing self test)
when eCryptfs is benchmarked.
Sometimes, only one format fails with ./john --test:
dynamic_87 [sha512(sha512($s).sha512($p)) 64/64 6144x1 sha2-OpenSSL]...
(8xOMP) FAILED (get_hash[0](6))
With unstable, all formats work.
For a non-OMP build of linux-x86-64-native, bleeding works as well.
Frank
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.
