(09-29-2017, 04:35 PM)philsmd Wrote: You just edited your post.... my guess is that you just did something wrong with your conversion... the first 512 bytes should suffice...
the problem is that you used hex encoded data... not the raw data (which is the only correct input)
Thank you for your answer.
You should have already noticed by now that I am a noob ^^ - sorry for that.
I try to get better.
But now I know exactly what went wrong.
Quote:the first 512 bytes should suffice...
I do not think so.
Maybe I again did not understand what you just said with hex, binary, raw or whatever data.
What I did is
--> took my original containers
--> opened them in Hexeditor
--> copied the first 299008 bytes (in Hex!)
--> pasted the Hex-Data with the same Hexeditor into a new file and called it Hash.txt
I did this with all my 4 created containers and used:
Code:
hashcat64.exe -m 13721 -a 3 Hash1.txt mi?l
hashcat64.exe -m 13723 -a 3 Hash2.txt mi?l
hashcat64.exe -m 13731 -a 3 Hash3.txt mi?l
hashcat64.exe -m 13733 -a 3 Hash4.txt mi?l
pauseThen came the success:
Quote:C:\TestAreal>hashcat64.exe -m 13721 -a 3 Hash1.txt mi?l
hashcat (v3.6.0) starting...
* Device #1: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: GeForce GTX 1080, 2048/8192 MB allocatable, 20MCU
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
* Single-Hash
* Single-Salt
* Brute-Force
* Uses-64-Bit
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c
The wordlist or mask that you are using is too small.
This means that hashcat cannot use the full parallel power of your device(s).
Unless you supply more work, your cracking speed will drop.
For tips on supplying more work, see: https://hashcat.net/faq/morework
Approaching final keyspace - workload adjusted.
Cracking performance lower than expected? Append -w 3 to the commandline.
Hash1.txt:mic
Session..........: hashcat
Status...........: Cracked
Hash.Type........: VeraCrypt PBKDF2-HMAC-SHA512 + XTS 512 bit
Hash.Target......: Hash1.txt
Time.Started.....: Fri Sep 29 16:39:53 2017 (8 secs)
Time.Estimated...: Fri Sep 29 16:40:01 2017 (0 secs)
Guess.Mask.......: mi?l [3]
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....: 0 H/s (0.28ms)
Recovered........: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.........: 26/26 (100.00%)
Rejected.........: 0/26 (0.00%)
Restore.Point....: 0/26 (0.00%)
Candidates.#1....: min -> miq
HWMon.Dev.#1.....: Temp: 53c Fan: 33% Util: 81% Core:2037MHz Mem:4714MHz Bus:16
Started: Fri Sep 29 16:39:51 2017
Stopped: Fri Sep 29 16:40:02 2017
C:\TestAreal>hashcat64.exe -m 13723 -a 3 Hash2.txt mi?l
hashcat (v3.6.0) starting...
* Device #1: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: GeForce GTX 1080, 2048/8192 MB allocatable, 20MCU
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
* Single-Hash
* Single-Salt
* Brute-Force
* Uses-64-Bit
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c
The wordlist or mask that you are using is too small.
This means that hashcat cannot use the full parallel power of your device(s).
Unless you supply more work, your cracking speed will drop.
For tips on supplying more work, see: https://hashcat.net/faq/morework
Approaching final keyspace - workload adjusted.
Cracking performance lower than expected? Append -w 3 to the commandline.
Hash2.txt:mic
Session..........: hashcat
Status...........: Cracked
Hash.Type........: VeraCrypt PBKDF2-HMAC-SHA512 + XTS 1536 bit
Hash.Target......: Hash2.txt
Time.Started.....: Fri Sep 29 16:40:09 2017 (22 secs)
Time.Estimated...: Fri Sep 29 16:40:31 2017 (0 secs)
Guess.Mask.......: mi?l [3]
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....: 0 H/s (0.64ms)
Recovered........: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.........: 26/26 (100.00%)
Rejected.........: 0/26 (0.00%)
Restore.Point....: 0/26 (0.00%)
Candidates.#1....: min -> miq
HWMon.Dev.#1.....: Temp: 53c Fan: 33% Util: 92% Core:2037MHz Mem:4714MHz Bus:16
Started: Fri Sep 29 16:40:02 2017
Stopped: Fri Sep 29 16:40:32 2017
C:\TestAreal>hashcat64.exe -m 13731 -a 3 Hash3.txt mi?l
hashcat (v3.6.0) starting...
* Device #1: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: GeForce GTX 1080, 2048/8192 MB allocatable, 20MCU
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
* Single-Hash
* Single-Salt
* Brute-Force
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c
The wordlist or mask that you are using is too small.
This means that hashcat cannot use the full parallel power of your device(s).
Unless you supply more work, your cracking speed will drop.
For tips on supplying more work, see: https://hashcat.net/faq/morework
Approaching final keyspace - workload adjusted.
Cracking performance lower than expected? Append -w 3 to the commandline.
Hash3.txt:mic
Session..........: hashcat
Status...........: Cracked
Hash.Type........: VeraCrypt PBKDF2-HMAC-Whirlpool + XTS 512 bit
Hash.Target......: Hash3.txt
Time.Started.....: Fri Sep 29 16:40:34 2017 (25 secs)
Time.Estimated...: Fri Sep 29 16:40:59 2017 (0 secs)
Guess.Mask.......: mi?l [3]
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....: 0 H/s (0.74ms)
Recovered........: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.........: 26/26 (100.00%)
Rejected.........: 0/26 (0.00%)
Restore.Point....: 0/26 (0.00%)
Candidates.#1....: min -> miq
HWMon.Dev.#1.....: Temp: 53c Fan: 37% Util: 91% Core:2037MHz Mem:4714MHz Bus:16
Started: Fri Sep 29 16:40:32 2017
Stopped: Fri Sep 29 16:41:00 2017
C:\TestAreal>hashcat64.exe -m 13733 -a 3 Hash4.txt mi?l
hashcat (v3.6.0) starting...
* Device #1: WARNING! Kernel exec timeout is not disabled.
This may cause "CL_OUT_OF_RESOURCES" or related errors.
To disable the timeout, see: https://hashcat.net/q/timeoutpatch
OpenCL Platform #1: NVIDIA Corporation
======================================
* Device #1: GeForce GTX 1080, 2048/8192 MB allocatable, 20MCU
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
* Single-Hash
* Single-Salt
* Brute-Force
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger set to 75c
The wordlist or mask that you are using is too small.
This means that hashcat cannot use the full parallel power of your device(s).
Unless you supply more work, your cracking speed will drop.
For tips on supplying more work, see: https://hashcat.net/faq/morework
Approaching final keyspace - workload adjusted.
Cracking performance lower than expected? Append -w 3 to the commandline.
Hash4.txt:mic
Session..........: hashcat
Status...........: Cracked
Hash.Type........: VeraCrypt PBKDF2-HMAC-Whirlpool + XTS 1536 bit
Hash.Target......: Hash4.txt
Time.Started.....: Fri Sep 29 16:41:07 2017 (55 secs)
Time.Estimated...: Fri Sep 29 16:42:02 2017 (0 secs)
Guess.Mask.......: mi?l [3]
Guess.Queue......: 1/1 (100.00%)
Speed.Dev.#1.....: 0 H/s (0.81ms)
Recovered........: 1/1 (100.00%) Digests, 1/1 (100.00%) Salts
Progress.........: 26/26 (100.00%)
Rejected.........: 0/26 (0.00%)
Restore.Point....: 0/26 (0.00%)
Candidates.#1....: min -> miq
HWMon.Dev.#1.....: Temp: 52c Fan: 33% Util: 93% Core:2037MHz Mem:4714MHz Bus:16
Started: Fri Sep 29 16:41:00 2017
Stopped: Fri Sep 29 16:42:02 2017
C:\TestAreal>pause
Drücken Sie eine beliebige Taste . . .
Do you believe me with the 299008 bytes?
So what about editing the wiki?