Hex ch and small problem

[ccprime]

hi
now DES is supported but i still have problems to figure out it

Code:

hashcat64.exe -m 14000 "C:\test3des.txt" -w 3 -a 3 -o "C:\test3desresult.txt"

input file looks:

Code:

47DC9810ADE39295:A04AB36B33E34FF2

and from log:

Code:

Session..........: hashcat
Status...........: Running
Hash.Type........: DES (PT = $salt, key = $pass)
Hash.Target......: 47dc9810ade39295:a04ab36b33e34ff2
Time.Started.....: Fri Feb 03 20:16:07 2017 (8 secs)
Time.Estimated...: Fri Feb 03 22:26:51 2017 (2 hours, 10 mins)
Input.Mask.......: ?1?2?2?2?2?2?2?3 [8]
Input.Charset....: -1 ?l?d?u, -2 ?l?d, -3 ?l?d*!$@_, -4 Undefined
Input.Queue......: 1/1 (100.00%)
Speed.Dev.#2.....:   235.1 MH/s (56.64ms)
Speed.Dev.#3.....:   235.1 MH/s (57.06ms)
Speed.Dev.#4.....:   235.1 MH/s (57.36ms)
Speed.Dev.#*.....:   705.4 MH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 5261426688/5533380698112 (0.10%)
Rejected.........: 0/5261426688 (0.00%)
Restore.Point....: 14336/68864256 (0.02%)
Candidates.#2....: j5rghzan -> T1tw1669
Candidates.#3....: j5rzldon -> T1tnsy23
Candidates.#4....: j5rt1ban -> T1t2s801
HWMon.Dev.#2.....: Temp: 37c Fan: 33%
HWMon.Dev.#3.....: Temp: 46c Fan: 33%
HWMon.Dev.#4.....: Temp: 40c Fan: 33%

INFO: approaching final keyspace, workload adjusted

Session..........: hashcat
Status...........: Exhausted
Hash.Type........: DES (PT = $salt, key = $pass)
Hash.Target......: 47dc9810ade39295:a04ab36b33e34ff2
Time.Started.....: Fri Feb 03 20:16:07 2017 (2 hours, 11 mins)
Time.Estimated...: Fri Feb 03 22:27:45 2017 (0 secs)
Input.Mask.......: ?1?2?2?2?2?2?2?3 [8]
Input.Charset....: -1 ?l?d?u, -2 ?l?d, -3 ?l?d*!$@_, -4 Undefined
Input.Queue......: 1/1 (100.00%)
Speed.Dev.#2.....:   213.1 MH/s (51.82ms)
Speed.Dev.#3.....:   213.1 MH/s (52.14ms)
Speed.Dev.#4.....:   213.5 MH/s (52.19ms)
Speed.Dev.#*.....:   639.8 MH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 5533380698112/5533380698112 (100.00%)
Rejected.........: 0/5533380698112 (0.00%)
Restore.Point....: 68839510/68864256 (99.96%)
Candidates.#2....: n4qzblq$ -> Xvq6x7q$
Candidates.#3....: n4q8u2q$ -> Xvq2dtq$
Candidates.#4....: n4qd2jx$ -> Xvqqzqg*
HWMon.Dev.#2.....: Temp: 66c Fan: 33%
HWMon.Dev.#3.....: Temp: 72c Fan: 79%
HWMon.Dev.#4.....: Temp: 74c Fan: 61%

Started: Fri Feb 03 20:16:00 2017
Stopped: Fri Feb 03 22:27:46 2017

now, when i do like this:

Code:

hashcat64.exe -m 14000 "C:\test3des.txt" -w 3 -a 3 -1 ?b?b?b?b?b?b?b?b -o "C:\test3desresult.txt"

with ?b?b?b?b?b?b?b?b then in log i have:

Code:

Input.Mask.......: ?1?2?2?2?2?2?2?3 [8]
Input.Charset....: -1 ?l?d?u, -2 ?l?d, -3 ?l?d*!$@_, -4 Undefined

it always give's me default charset
how to do it correct ??
and why when i change hash type from 14000 to 14100 i have "Invalid mask" ?? it's only key len diferent
what i do wrong ??



i read all wiki, faq's, post's etc etc, and i'm still confused

[philsmd]

It seems that you are mixing up custom charsets (-1 xxx) with the mask itself.
This makes no sense: -a 3 -1 ?b?b?b?b?b?b?b?b

-1 is the same as --custom-charset1 and it is used to define a custom charset (a set of characters)
what you probably wanted instead is to run this:

Code:

hashcat64.exe -m 14000 -a 3 -w 3 -o "C:\test3desresult.txt" "C:\test3des.txt" ?b?b?b?b?b?b?b?b

[ccprime]

"The wordlist or mask you are using is too small."

Code:

OpenCL Platform #1: Advanced Micro Devices, Inc.
================================================
* Device #1: AMD FX(tm)-8320 Eight-Core Processor           , skipped

OpenCL Platform #2: NVIDIA Corporation
======================================
* Device #2: GeForce GTX 660 Ti, 512/2048 MB allocatable, 7MCU
* Device #3: GeForce GTX 660 Ti, 512/2048 MB allocatable, 7MCU
* Device #4: GeForce GTX 660 Ti, 512/2048 MB allocatable, 7MCU

Hashes: 1 digests; 1 unique digests, 1 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates

Applicable Optimizers:
* Zero-Byte
* Precompute-Final-Permutation
* Not-Iterated
* Single-Hash
* Single-Salt
* Brute-Force

Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c

The wordlist or mask you are using is too small.
Therefore, hashcat is unable to utilize the full parallelization power of your device(s).
The cracking speed will drop.
Workaround: https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#how_to_create_more_work_for_full_speed

INFO: approaching final keyspace, workload adjusted

INFO: approaching final keyspace, workload adjusted

INFO: approaching final keyspace, workload adjusted

Session..........: hashcat
Status...........: Exhausted
Hash.Type........: DES (PT = $salt, key = $pass)
Hash.Target......: 47dc9810ade39295:a04ab36b33e34ff2
Time.Started.....: Sat Feb 04 09:01:03 2017 (0 secs)
Time.Estimated...: Sat Feb 04 09:01:03 2017 (0 secs)
Input.Mask.......: ?b?b?b?b?b?b?b?b [8]
Input.Queue......: 1/1 (100.00%)
Speed.Dev.#2.....:        0 H/s (0.00ms)
Speed.Dev.#3.....:        0 H/s (0.00ms)
Speed.Dev.#4.....:        0 H/s (0.00ms)
Speed.Dev.#*.....:        0 H/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 0
Rejected.........: 0
Restore.Point....: 0
Candidates.#2....: [Generating]
Candidates.#3....: [Generating]
Candidates.#4....: [Generating]
HWMon.Dev.#2.....: Temp: 33c Fan: 30%
HWMon.Dev.#3.....: Temp: 38c Fan: 32%
HWMon.Dev.#4.....: Temp: 35c Fan: 10%

Started: Sat Feb 04 09:00:56 2017
Stopped: Sat Feb 04 09:01:04 2017

[philsmd]

The problem here might be that the keyspace is way too huge and therefore a "integer overflow" is reached. 255^8 = 17878103347812890625 (yeah, a huge number!).

Try with a smaller mask instead...

BTW: you should better use the built-in charset, so something like this:

Code:

hashcat64.exe -m 14000 -a 3 -w 3 --hex-charset -1 charsets/DES_full.charset -o "C:\testdesresult.txt" "C:\testdes.txt" ?1?1?1?1?1?1?1?1

[ccprime]

thanks 
thats works
its show me just 3 years on -w 4
w3 show 60 days more
but i still have a question, why we cannot use ?b in cmd line ?
and what about 14100 ? should i DES_full.charset make it double inside ?
now i cannot figure out 14100 :/

[atom]

?b doesn't make sense because DES strips the highest bit and you'll end up with a 56 bit keyspace. That's what DES_full.charset is optimized for, to search only within this 56 bit keyspace.

[ccprime]

and what about 3des ?
use the same charset file ?

[ccprime]

i made few tests, just to check the max time to find key

DES tests:

with those parameters i have 3 years 61 days
-1 charsets/DES_full.charset
?1?1?1?1?1?1?1?1

with this 1 year 59 days
-1 charsets/DES_full.charset
-2 charsets/DES_0_9.charset
?2?1?1?1?1?1?1?1
where DES_0_9.charset is without ABCDEF

Code:

0103050709111315171921232527293133353739414345474951535557596163656769717375777981838587891939597999

with this 9 days 2 hours
-1 charsets/DES_full.charset
-2 charsets/DES_one_byte.charset
?2?1?1?1?1?1?1?1
where DES_one_byte.charset is only one byte 00



but for 3des when i use
-1 charsets/DES_full.charset
-2 charsets/DES_one_byte.charset
?2?2?2?2?2?2?2?2?2?2?2?2?2?2?2?1
i have

Code:

Skipping mask '?2?2?2?2?2?2?2?2?2?2?2?2?2?2?2?1' because it is smaller than the minimum password length
The wordlist or mask you are using is too small.
Therefore, hashcat is unable to utilize the full parallelization power of your device(s).
The cracking speed will drop.
Workaround: https://hashcat.net/wiki/doku.php?id=frequently_asked_questions#how_to_create_more_work_for_full_speed

INFO: approaching final keyspace, workload adjusted

INFO: approaching final keyspace, workload adjusted

INFO: approaching final keyspace, workload adjusted

Session..........: hashcat
Status...........: Exhausted
Hash.Type........: 3DES (PT = $salt, key = $pass)
Hash.Target......: 47dc9810ade39295:d7d0c92e0af05819
Time.Started.....: Wed Feb 08 23:00:52 2017 (0 secs)
Time.Estimated...: Wed Feb 08 23:00:52 2017 (0 secs)
Input.Mask.......: ?2?2?2?2?2?2?2?2?2?2?2?2?2?2?2?1 [16]
Input.Charset....: -1 charsets/DES_full.charset, -2 charsets/DES_one_byte.charset, -3 Undefined, -4 Undefined
Input.Queue......: 1/1 (100.00%)
Speed.Dev.#2.....:        0 H/s (0.00ms)
Speed.Dev.#3.....:        0 H/s (0.00ms)
Speed.Dev.#4.....:        0 H/s (0.00ms)
Speed.Dev.#*.....:        0 H/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 0
Rejected.........: 0
Restore.Point....: 0
Candidates.#2....: [Generating]
Candidates.#3....: [Generating]
Candidates.#4....: [Generating]
HWMon.Dev.#2.....: Temp: 43c Fan: 32%
HWMon.Dev.#3.....: Temp: 49c Fan: 37%
HWMon.Dev.#4.....: Temp: 47c Fan: 10%

Started: Wed Feb 08 23:00:37 2017
Stopped: Wed Feb 08 23:00:54 2017

1. how to run 3des ? what i do wrong ? its just a len of key 16 not 8
2. can someone who have x4 1080 show me max time for DES and 3DES ?

[atom]

with this 1 year 59 days
-1 charsets/DES_full.charset
-2 charsets/DES_0_9.charset
?2?1?1?1?1?1?1?1
where DES_0_9.charset is without ABCDEF

This totally makes no sense. Do not confuse a key with a password.

1. how to run 3des ? what i do wrong ? its just a len of key 16 not 8

For 3des you need a key with exactly 24 octets, not 8. there no way to bf this

2. can someone who have x4 1080 show me max time for DES and 3DES ?

Here's DES with 4x1080:

Speed.Dev.#1.....: 18980.3 MH/s (70.47ms)
Speed.Dev.#2.....: 18753.7 MH/s (71.36ms)
Speed.Dev.#3.....: 19016.5 MH/s (70.36ms)
Speed.Dev.#4.....: 18997.7 MH/s (70.38ms)
Speed.Dev.#*.....: 75748.2 MH/s
Time.Estimated...: Sun Feb 19 11:00:20 2017 (11 days, 0 hours)

As I said, you can't BF 3des keyspace (integer overflow, too).

[ccprime]

Here's DES with 4x1080:

Speed.Dev.#1.....: 18980.3 MH/s (70.47ms)
Speed.Dev.#2.....: 18753.7 MH/s (71.36ms)
Speed.Dev.#3.....: 19016.5 MH/s (70.36ms)
Speed.Dev.#4.....: 18997.7 MH/s (70.38ms)
Speed.Dev.#*.....: 75748.2 MH/s
Time.Estimated...: Sun Feb 19 11:00:20 2017 (11 days, 0 hours)

As I said, you can't BF 3des keyspace (integer overflow, too).

thx for respond atom@
now i know lots of more
thx again

btw about 3des and integer overflow/buffer overflow
maybe hashcat should be slower for 3des, not made so many instructions
it can be fixed
is this possible to fix it ?
just to make it work