[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP407664F47ABE1FA8F4DE61CFDCD0@phx.gbl>
Date: Tue, 16 Apr 2013 16:30:49 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Segfault for linux-x86-native with -DDEBUG added (was: Segfault for
hdaa on linux-x86-clang-debug)
On 04/16/2013 01:32 PM, Frank Dittrich wrote:
> Since this points to a possible problem in the format itself, and not in
> the -DDEBUG code, here are all the formats that fail for
> linux-x86-clang-debug:
>
> hdaa ipb2 mschapv2 netntlm nt2 xsha mscash2 oracle11 raw-md5u sapb sapg
> sunmd5 wpapsk
Turns out the problem is not limited to clang, but can be triggered with
gcc as well, by just adding -DDEBUG to CFLAGS:
(unstable-jumbo)run $ for f in hdaa ipb2 mschapv2 netntlm nt2 xsha
mscash2 oracle11 raw-md5u sapb sapg sunmd5 wpapsk; do ./john --test=0
--format=$f; done
Warning: doing quick benchmarking - the performance numbers will be
inaccurate
Benchmarking: HTTP Digest access authentication MD5 [128/128 SSE2
intrinsics 12x]... Segmentation fault (core dumped)
Warning: doing quick benchmarking - the performance numbers will be
inaccurate
Benchmarking: Invision Power Board 2.x salted MD5 [128/128 SSE2
intrinsics 12x]... Segmentation fault (core dumped)
Warning: doing quick benchmarking - the performance numbers will be
inaccurate
Benchmarking: MSCHAPv2 C/R MD4 DES [128/128 SSE2 intrinsics 12x]...
Rejected MSCHAPv2 hash with invalid 3rd block
Rejected MSCHAPv2 hash with invalid 3rd block
Rejected MSCHAPv2 hash with invalid 3rd block
Rejected MSCHAPv2 hash with invalid 3rd block
Segmentation fault (core dumped)
Warning: doing quick benchmarking - the performance numbers will be
inaccurate
Benchmarking: NTLMv1 C/R MD4 DES (ESS MD5) [128/128 SSE2 intrinsics
12x]... Segmentation fault (core dumped)
Warning: doing quick benchmarking - the performance numbers will be
inaccurate
Benchmarking: NT MD4 [128/128 SSE2 intrinsics 12x]... Segmentation fault
(core dumped)
Warning: doing quick benchmarking - the performance numbers will be
inaccurate
Benchmarking: Mac OS X 10.4 - 10.6 salted SHA-1 [128/128 SSE2 4x]...
Segmentation fault (core dumped)
Warning: doing quick benchmarking - the performance numbers will be
inaccurate
Benchmarking: M$ Cache Hash 2 (DCC2) PBKDF2-HMAC-SHA-1 [128/128 SSE2
4x]... Segmentation fault (core dumped)
Warning: doing quick benchmarking - the performance numbers will be
inaccurate
Benchmarking: Oracle 11g SHA-1 [128/128 SSE2 4x]... Segmentation fault
(core dumped)
Warning: doing quick benchmarking - the performance numbers will be
inaccurate
Benchmarking: md5(unicode($p)) [128/128 SSE2 intrinsics 12x]...
Segmentation fault (core dumped)
Warning: doing quick benchmarking - the performance numbers will be
inaccurate
Benchmarking: SAP CODVN B (BCODE) [128/128 SSE2 intrinsics 12x]...
Segmentation fault (core dumped)
Warning: doing quick benchmarking - the performance numbers will be
inaccurate
Benchmarking: SAP CODVN F/G (PASSCODE) [128/128 SSE2 4x]... Segmentation
fault (core dumped)
Warning: doing quick benchmarking - the performance numbers will be
inaccurate
Benchmarking: SunMD5 [128/128 SSE2 intrinsics 12x x576]... Segmentation
fault (core dumped)
Warning: doing quick benchmarking - the performance numbers will be
inaccurate
Benchmarking: WPA-PSK PBKDF2-HMAC-SHA-1 [128/128 SSE2 4x]...
Segmentation fault (core dumped)
(unstable-jumbo)run $
May be all these formats (and may be even more formats) need proper
alignment specified for all variables which end up being passed to sse2
functions?
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.
