Hey
So I keep getting the error every time I try run the crack. I know I have ran the right mode in cmd as they are md5 hashes. Basically all I have done is copied all my hashes which I have in a excel document and copied them into my hash text file in my hashcat folder. I have looked around the web and YouTube but not sure what is causing this problem. Is there more I need to copy into my hash text file?
BTW I am of course on windows 10. Any help would be appreciated.
Posts: 12
Threads: 4
Joined: Sep 2017
(09-15-2017, 12:26 AM)AtomTan Wrote: Hey
So I keep getting the error every time I try run the crack. I know I have ran the right mode in cmd as they are md5 hashes. Basically all I have done is copied all my hashes which I have in a excel document and copied them into my hash text file in my hashcat folder. I have looked around the web and YouTube but not sure what is causing this problem. Is there more I need to copy into my hash text file?
BTW I am of course on windows 10. Any help would be appreciated.
This is the what happens when i run the command hashcat64.exe -m 0 -a3 -o cracked.txt hash.txt wordlists/
then i get the following message
Hash hash.txt : line length exception
No hashes loaded
Anybody who could help me?
Posts: 301
Threads: 2
Joined: Dec 2015
Well, first you should probably be specifying -a 0, not -a 3 since you seem to trying to load wordlists, not a mask. Second, it seems like your hash.txt file is empty, since hashcat is unable to find any hashes in it. Please make sure that the hashes are present in the file, and are formatted correctly, 1 per line.
Posts: 2,302
Threads: 11
Joined: Jul 2010
actually it looks like hashcat cannot find your hash.txt file at all.
Posts: 301
Threads: 2
Joined: Dec 2015
09-15-2017, 09:39 PM
(This post was last modified: 09-15-2017, 09:40 PM by Chick3nman.)
(09-15-2017, 06:27 PM)undeath Wrote: actually it looks like hashcat cannot find your hash.txt file at all.
Actually, you are right. Looking at it again, it’s not loading a blank line as a hash, it’s loading «hash.txt» as the literal hash instead of as a file path. Good catch!
Posts: 12
Threads: 4
Joined: Sep 2017
09-16-2017, 09:58 PM
(This post was last modified: 09-16-2017, 09:58 PM by AtomTan.)
(09-15-2017, 09:39 PM)Chick3nman Wrote:
(09-15-2017, 06:27 PM)undeath Wrote: actually it looks like hashcat cannot find your hash.txt file at all.
Actually, you are right. Looking at it again, it’s not loading a blank line as a hash, it’s loading «hash.txt» as the literal hash instead of as a file path. Good catch!
Untitled.png (Size: 135.28 KB / Downloads: 71)
Untitled2.jpg (Size: 136.75 KB / Downloads: 63)
This is what it looks like as you can see the files is in the directory and the hashes notepad has got hashes pasted into it and it so it is not empty. I have tried everything. Using all sorts of different hash types. Dont know what else to do.
Posts: 2,302
Threads: 11
Joined: Jul 2010
Your windows is configured to not show known file extensions. That might have something to do with your problem.
Posts: 12
Threads: 4
Joined: Sep 2017
(09-16-2017, 10:05 PM)undeath Wrote: Your windows is configured to not show known file extensions. That might have something to do with your problem.
Ok sorry for the noob question then but how can I fix windows so I can finally try out hashcat?
Posts: 12
Threads: 4
Joined: Sep 2017
(09-16-2017, 10:05 PM)undeath Wrote: Your windows is configured to not show known file extensions. That might have something to do with your problem.
Ok sorry for the noob question then but how can I fix windows so I can finally try out hashcat?
Posts: 12
Threads: 4
Joined: Sep 2017
Ok CooI I got the problem sorted. The hash.txt was not saved as unicode format. Thanks for help.
What version of your hashcat?
kali@kali:$ hashcat --version
v5.1.0
kali@kali:$
There are a few types of md5 supported by hashcat
kali@kali:$ hashcat -h | grep md5
10 | md5($pass.$salt) | Raw Hash, Salted and/or Iterated
20 | md5($salt.$pass) | Raw Hash, Salted and/or Iterated
30 | md5(utf16le($pass).$salt) | Raw Hash, Salted and/or Iterated
40 | md5($salt.utf16le($pass)) | Raw Hash, Salted and/or Iterated
3800 | md5($salt.$pass.$salt) | Raw Hash, Salted and/or Iterated
3710 | md5($salt.md5($pass)) | Raw Hash, Salted and/or Iterated
4010 | md5($salt.md5($salt.$pass)) | Raw Hash, Salted and/or Iterated
4110 | md5($salt.md5($pass.$salt)) | Raw Hash, Salted and/or Iterated
2600 | md5(md5($pass)) | Raw Hash, Salted and/or Iterated
3910 | md5(md5($pass).md5($salt)) | Raw Hash, Salted and/or Iterated
4300 | md5(strtoupper(md5($pass))) | Raw Hash, Salted and/or Iterated
4400 | md5(sha1($pass)) | Raw Hash, Salted and/or Iterated
4700 | sha1(md5($pass)) | Raw Hash, Salted and/or Iterated
1600 | Apache $apr1$ MD5, md5apr1, MD5 (APR) | HTTP, SMTP, LDAP Server
500 | md5crypt, MD5 (Unix), Cisco-IOS $1$ (MD5) | Operating Systems
6300 | AIX {smd5} | Operating Systems
kali@kali:$
If you check your hash with hashid, you’ll find out that this is actually MD5 Crypt
kali@kali:$ hashid '$1$FTpMLT88$VdzDQTTcksukSKMLRSVlc.'
Analyzing '$1$FTpMLT88$VdzDQTTcksukSKMLRSVlc.'
[+] MD5 Crypt
[+] Cisco-IOS(MD5)
[+] FreeBSD MD5
kali@kali:$
There is only 1 md5crypt, and the code number is 500
kali@kali:$ hashcat -h | grep md5.*cry
500 | md5crypt, MD5 (Unix), Cisco-IOS $1$ (MD5) | Operating Systems
kali@kali:$
Try again with correct hash mode which is 500 for this case
Try again … voilà
kali@kali:~$ hashcat -m 500 -a 0 md5crypt.txt rockyou.txt
hashcat (v4.0.1) 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
nvmlDeviceGetFanSpeed(): Not Supported
OpenCL Platform #1: NVIDIA Corporation
======================================
Hashes: 3 digests; 3 unique digests, 3 unique salts
Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates
Rules: 1
Applicable optimizers:
* Zero-Byte
Password length minimum: 0
Password length maximum: 256
ATTENTION! Pure (unoptimized) OpenCL kernels selected.
This enables cracking passwords and salts > length 32 but for the price of drastical reduced performance.
If you want to switch to optimized OpenCL kernels, append -O to your commandline.
Watchdog: Temperature abort trigger set to 90c
Watchdog: Temperature retain trigger disabled.
* Device #1: build_opts '-I /usr/share/hashcat/OpenCL -D VENDOR_ID=32 -D CUDA_ARCH=601 -D AMD_ROCM=0 -D VECT_SIZE=1 -D DEVICE_TYPE=4 -D DGST_R0=0 -D DGST_R1=1 -D DGST_R2=2 -D DGST_R3=3 -D DGST_ELEM=4 -D KERN_TYPE=500 -D _unroll'
* Device #1: Kernel m00500.c2bb92e8.kernel not found in cache! Building may take a while...
* Device #1: Kernel amp_a0.e98c1de0.kernel not found in cache! Building may take a while...
Dictionary cache built:
* Filename..: rockyou.txt
* Passwords.: 14344392
* Bytes.....: 139921507
* Keyspace..: 14344385
* Runtime...: 2 secs
- Device #1: autotuned kernel-accel to 128
- Device #1: autotuned kernel-loops to 250
I’m a beginner in cryptography and I was deciphering a list of md5 hashes using hashcat 6.2.5,
the problems that I faced were:
- my cmd didn’t recognize hashcat64.exe as a command but accepted hashcat.exe as a command
- my text docs don’t visually show the .txt extension but are indeed .txt files when checked with properties or path
- decoding a list of hashes, I used the -m 0 and -a 0 command but when executed, gave the «token exception length, no hashes loaded» error.
how to resolve this issue?
- windows
- security
- password-encryption
- hashcat
asked Jan 27, 2022 at 12:48
2
-
it would be great if you put some of the hashes to see so we can investigate more
Jan 28, 2022 at 10:27
-
sure, e10adc3949ba59abbe56e057f20f883e 25f9e794323b453885f5181f1b624d0b
Feb 3, 2022 at 10:06
Posts: 10
Threads: 2
Joined: Nov 2018
Reputation:
0
Trying to crack IKE PSK MD5 (-m 5300)
Client: python 0.3.0 version
OS: Windows 8.1
I got an error «HC error: No hashes loaded»
Here is the debug output:
Quote:[2018-11-07 10:43:25,641] [DEBUG] b'{«action»:»getChunk»,»response»:»SUCCESS»,»status»:»OK»,»chunkId»:3,»skip»:0,»length»:1}’
[2018-11-07 10:43:25,641] [INFO ] Start chunk…
[2018-11-07 10:43:25,643] [DEBUG] CALL: hashcat64.exe —machine-readable —quiet —status —remove —restore-disable —potfile-disable —session=hashtopolis —status-timer 5 —outfile-check-timer=5 —outfile-check-dir=….hashlist_1 -o ….hashlists1.out —outfile-format=15 -p » « —remove-timer=5 -s 0 -l 1 -a 0 ….hashlists1 ….filesmydict.dict —hash-type=5300
[2018-11-07 10:43:25,644] [DEBUG] started cracking
[2018-11-07 10:43:26,814] [ERROR] HC error: No hashes loaded.
[2018-11-07 10:43:26,815] [DEBUG] {‘action’: ‘clientError’, ‘token’: ‘XXXXXXXXXX’, ‘taskId’: 1, ‘message’: ‘No hashes loaded.’}
[2018-11-07 10:43:28,269] [DEBUG] http://server-ip:80 «POST /hashtopolis/api/server.php HTTP/1.1» 200 45
[2018-11-07 10:43:29,350] [DEBUG] b'{«action»:»clientError»,»response»:»SUCCESS»}’
[2018-11-07 10:43:30,452] [INFO ] finished chunk
I think the problem is in -p option with chr(9) value. I tried to run hashcat in manual mode. And if I delete -p option all is OK. But I cant get good result with -p option at all even I changed it’s value.
Thanx for any solution
Posts: 154
Threads: 6
Joined: Oct 2018
Reputation:
6
The chr(9) character should not be a problem on windows, I tested the client regularly on windows and -p was never an issue. We are using the tab character to avoid all these issues when having separators which are present in hashes.
Did you verify that on the client in the file hashlists/1 there is actually the correct hash? In case there was an error on the download it might be empty.
I will do a test tomorrow and look if there might be a problem with this kind of binary hashes.
Posts: 10
Threads: 2
Joined: Nov 2018
Reputation:
0
(11-07-2018, 11:26 PM)s3in!c Wrote: The chr(9) character should not be a problem on windows, I tested the client regularly on windows and -p was never an issue. We are using the tab character to avoid all these issues when having separators which are present in hashes.
Did you verify that on the client in the file hashlists/1 there is actually the correct hash? In case there was an error on the download it might be empty.
I will do a test tomorrow and look if there might be a problem with this kind of binary hashes.
I verified the hashlists/1 file first of all. And it had correct hash.
Then I tried to run the same command in command prompt. And until I deleted -p param hashcat had given me the same error
Code:
Hashfile '....hashlists1' on line 1 (e957a6...19a3428d90eb5045363a58dc33f51941): Separator unmatched
No hashes loaded.
I added hash file, dict file and bat file to this post.
Files.zip (Size: 949 bytes / Downloads: 5)
Posts: 154
Threads: 6
Joined: Oct 2018
Reputation:
6
11-08-2018, 07:48 AM
(This post was last modified: 11-08-2018, 08:25 AM by s3in!c.)
Thanks for the information. Indeed it’s a separator issue, it’s the same reason like for the hash parsing I fixed in this pull request: https://github.com/hashcat/hashcat/pull/1727
But as the hash was in a file, I didn’t check it. I’ll go over all algorithms again and fix the remaining ones and do again a pull request to hashcat.
Posts: 154
Threads: 6
Joined: Oct 2018
Reputation:
6
The fixed code is now in the hashcat repository: https://github.com/hashcat/hashcat/pull/1770
So either build hashcat from source there or wait until the next beta build or release. With the fix it will work within the hashtopolis agent and not throw anymore the separator unmatched error.
Posts: 10
Threads: 2
Joined: Nov 2018
Reputation:
0
Thx a lot. It works!
But I got another error: client doesn’t sent cracked hash to his server.
Here is the debug log:
Quote:[2018-11-13 03:47:27,634] [DEBUG] CALL: hashcat64.exe —machine-readable —quiet —status —remove —restore-disable —potfile-disable —session=hashtopolis —status-timer 5 —outfile-check-timer=5 —outfile-check-dir=….hashlist_1 -o ….hashlists1.out —outfile-format=15 -p » » —remove-timer=5 -s 0 -l 1 -a 0 ….hashlists1 ….filesmydict.dict —hash-type=5300
[2018-11-13 03:47:28,288] [DEBUG] started cracking
[2018-11-13 03:47:30,204] [DEBUG] STATUS 6 SPEED 4475 1000 EXEC_RUNTIME 0.029760 CURKU 0 PROGRESS 1 1 RECHASH 1 1 RECSALT 1 1 REJECTED 0 UTIL -1
[2018-11-13 03:47:30,206] [DEBUG] Sending 0 cracks…
STATUS 6 means hashcat has cracked my hash, but the client sends nothing to the server.
Hash, dictionary file are the same.
Posts: 154
Threads: 6
Joined: Oct 2018
Reputation:
6
I think this is the special case that the hash get cracked so fast that the agent stopped to read the output file too fast. This was a bug in the 0.3.0 client version, if you run a normal task, this should not happen.
I assume that this above is from the test task as the keyspace is only length 1. Please test with a slightly larger task (e.g. taking a few minutes time) if this still happens then. If it works with longer tasks, it’s definitely because of that known bug, in that case you could try with the `current-dev` branch of the client to make sure it is fixed.
Posts: 10
Threads: 2
Joined: Nov 2018
Reputation:
0
(11-13-2018, 12:38 PM)s3in!c Wrote: I think this is the special case that the hash get cracked so fast that the agent stopped to read the output file too fast. This was a bug in the 0.3.0 client version, if you run a normal task, this should not happen.
I assume that this above is from the test task as the keyspace is only length 1. Please test with a slightly larger task (e.g. taking a few minutes time) if this still happens then. If it works with longer tasks, it’s definitely because of that known bug, in that case you could try with the `current-dev` branch of the client to make sure it is fixed.
I have tested it with ‘current-dev’ branch and all is ok.
Thank you.
I tried to use Hashcat on a Word password-protected doc, but I got this error:
C:UsersUserDesktophashcat-5.1.0>hashcat64.exe hashcat -a 0 -m 9600 --username -o pass.txt hash.txt rockyou-withcount.txt
hashcat (v5.1.0) starting...
* Device #2: This hardware has outdated CUDA compute capability (3.0).
For modern OpenCL performance, upgrade to hardware that supports
CUDA compute capability version 5.0 (Maxwell) or higher.
* Device #2: 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
nvmlDeviceGetCurrPcieLinkWidth(): Not Supported
nvmlDeviceGetClockInfo(): Not Supported
nvmlDeviceGetClockInfo(): Not Supported
nvmlDeviceGetTemperatureThreshold(): Not Supported
nvmlDeviceGetTemperatureThreshold(): Not Supported
nvmlDeviceGetUtilizationRates(): Not Supported
OpenCL Platform #1: Intel(R) Corporation
========================================
* Device #1: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz, skipped.
OpenCL Platform #2: NVIDIA Corporation
======================================
* Device #2: GeForce GTX 760, 1024/4096 MB allocatable, 6MCU
Failed to parse hashes using the 'native hashcat' format.
No hashes loaded.
Started: Fri Dec 28 19:04:28 2018
Stopped: Fri Dec 28 19:04:28 2018
C:UsersUserDesktophashcat-5.1.0>
The file hash.txt:
$office$*2013*100000*256*16*caeeddcc432ce81fc337e7ebeaf222df*2e7ed78069479490aa256e9889b7405f*c2ece9296ccf8523e5c9f3bce0ea5d4a31f5df78d8ccfd7909b009e636dd17e0
How can I fix this issue?
Super Jade
2912 gold badges4 silver badges16 bronze badges
asked Dec 28, 2018 at 17:23
I know it’s old, but the problem here is that you have to remove the --username option if the hash file doesn’t contain the name of the document that you’re trying to crack
For example:
Using the option --username with the below hash file will lead to normal output without parsing errors
hash.txt:
File name.doc:
$office$*2013*100000*256*16*caeeddcc432ce81fc337e7ebeaf222df*2e7ed78069479490aa256e9889b7405f*c2ece9296ccf8523e5c9f3bce0ea5d4a31f5df78d8ccfd7909b009e636dd17e0
And using --username with your file which contain only the hash of the document will lead to parsing error.
answered Apr 23, 2019 at 14:37
