Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 20 Feb 2016 17:20:11 -0500
From: Alex <mysqlstudent@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: Cracking zip files

Hi,

> Default is to enable OpenMP, except for fast formats, which is what you got
> here.
> Fast formats don't benefit from OpenMP as much as expected, even if you
> enforce OpenMP support for them.
> So, for fast formats (those which don't have the "(8xOMP)" or similar text
> written in their --test output), you should use --fork=N (where N is the
> number of logical cores you have) instead.
>
> You can enable OpenMP even for fast formats, if you use
> ./configure --enable-openmp-for-fast-formats
...

Okay, I've left it simple for now, and just ran configure without any options.

Target CPU ................................. x86_64 SSE2, 64-bit LE
AES-NI support ............................. depends on OpenSSL
Target OS .................................. linux-gnu
Cross compiling ............................ no
Legacy arch header ......................... x86-64.h

Optional libraries/features found:
Fuzzing test ............................... no
Experimental code .......................... no
OpenMPI support (default disabled) ......... no
Fork support ............................... yes
OpenMP support ............................. yes (not for fast formats)
CUDA support (default disabled by OpenCL) .. no
OpenCL support ............................. no
Generic crypt(3) format .................... yes
Rexgen (extra cracking mode) ............... no
GMP (PRINCE mode and faster SRP formats) ... no
PCAP (vncpcap2john and SIPdump) ............ yes
Z (pkzip format, gpg2john) ................. yes
BZ2 (gpg2john extra decompression logic) ... no
128-bit integer (faster PRINCE mode) ....... yes
Memory map (share/page large files) ........ yes

Development options (these may hurt performance when enabled):
Memdbg memory debugging settings ........... disabled
AddressSanitizer ("ASan") .................. disabled
UndefinedBehaviorSanitizer ("UbSan") ....... disabled

I've posted my CPU in my first message, but here's the whole /proc/cpuinfo:

processor       : 5
vendor_id       : AuthenticAMD
cpu family      : 16
model           : 10
model name      : AMD Phenom(tm) II X6 1090T Processor
stepping        : 0
microcode       : 0x10000dc
cpu MHz         : 3210.771
cache size      : 512 KB
physical id     : 0
siblings        : 6
core id         : 5
cpu cores       : 6
apicid          : 5
initial apicid  : 5
fpu             : yes
fpu_exception   : yes
cpuid level     : 6
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext
fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl
nonstop_tsc extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm
cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch
osvw ibs skinit wdt nodeid_msr cpb hw_pstate npt lbrv svm_lock
nrip_save pausefilter vmmcall
bugs            : tlb_mmatch fxsave_leak sysret_ss_attrs
bogomips        : 6421.54
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate cpb

When I run john, I only get this now:

$ ./john --incremental zipfile.john
Using default input encoding: UTF-8
No password hashes loaded (see FAQ)

I realize this is a FAQ, but none of the answers in this FAQ question
have helped me figure this out. The previous version I was using was
working okay.

I've deleted the old attempts from the previous version and recreated
the hash file. This is the contents of the zipfile.john:

zipfile.zip:$zip$*0*3*de3c868ba87dcff820dd1f8123b6b02f*f96a:::::zipfile.zip

I really have no idea where to go from here :-(
Thanks,
Alex

Powered by blists - more mailing lists

Your e-mail address:

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.