[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 7 Apr 2013 15:50:10 +0200
From: Sandra Schlichting <littlesandra88@...il.com>
To: john-users@...ts.openwall.com
Subject: Re: What am I doing wrong?
> Yes, you can use an external mode to do it through "dumb force" (aaa, aab,
> aac, aad etc..), do you know how long they will be? The all possible
> combinations can be tried in minutes, days, months, years depending on
> length. The incremental and markov modes choose strings based on
> likelihood/statistics rather than just iterating through every possible
> combination in order. If the passwords are going to be over 8 characters,
> you will have to re-compile john so that it's incremental mode will work
> with more than 8 characters. Markov does not use the .chr files so it
> wouldn't be limited or need to be compiled to support longer lengths but it
> does have to be trained.
> http://openwall.info/wiki/john/markov (patch not needed if using latest
> sources)
>
That is very interesting!
So Marcow can not be stopped and resumed. Can Incremental that?
> You can train your markov stats on prefiltered wordlists that only contain
> the characters your looking for, and incremental as well.These should be
> faster methods than old brute foce aka dumb force. Might also be a good
> idea to use pure alpha word's from wordlists, and simply overstrike and or
> insert "dashes" in various places. I can help on the dumbforce, incremental
> and probably a gew wordlist rules but I've never used markov myself. If you
> have more info about these hashes it might help choose which methods to
> use.
It turned out that the "tdc" one was very simple to brute force using the
command I posted. CpU2ts
The other one have been brute forcing since Friday and only completed 0.04%
The passphrase have a max length of 29 chars and can by anything possible
on a French keyboard , but I will expect it to be 8 ASCII characters.
Can I ask a bonus question about compiling jtr?
I started the job on a "Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz"
wjich have these "flags" as "cat /proc/cpuinfo" calls them:
fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36
clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc
arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl
vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm dtherm tpr_shadow vnmi
flexpriority
and compiled it by
wget http://www.openwall.com/john/g/john-1.7.9-jumbo-7.tar.bz2
tar xjf john-1.7.9-jumbo-7.tar.bz2
cd john-1.7.9-jumbo-7/src/
make clean linux-x86-64
../run/john --format=raw-md5 /tmp/hashs
Is that the correct architecture I have chosen?
Reading the FAQ, it seams that if I want to use both cores, then I have to
hand schedule the jobs?
Given that I have started the job with
../run/john --format=raw-md5 /tmp/hashs
can I then stop it, split the remaining in two, and resume using both cores?
Hugs,
Sandra
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.
