Could not locate /home/fenix/hashtopussy/hashcat/1/hashcat-464.164.064.bin

[myhashs]

did all by manual but got this message

fenix@fenix-System-Product-Name:~/hashtopussy$ sudo mono ./hastopussy.exe Client Version 0.52.1 Connecting to server http://192.168.1.14/api/server.php System is Linux 64-bit Existing token found Sending server client information System is Linux 64-bit Logged in to server Checking for client updates You are using the latest client version Using new STATUS codes Getting task Server has assigned client with Task:4, Cracker:1 and Hashlist:2 Downloading hashlist for this task, please wait... Downloading from http://192.168.1.14/getHashlist.php?hashlists=2&token=SNOvg0MP13 Downloading 100% @ 6.89 MB/s Finished downloading file Client already exists, skipping download Getting chunk... Server has requested the client measure the keyspace for this task Could not locate /home/fenix/hashtopussy/hashcat/1/hashcat-464.164.064.bin Keyspace measuring was unsuccessful, check all files are present

help me pls tired to get this problem solve

[s3inlc]

What do you have as configuration values for the cracker binary on the server?

[myhashs]

Binary ID	Version	Binary Name	Download URL	Action
1	4.1.0	hashcat-4.1.0	https://hashcat.net/files/hashcat-4.1.0.7z

[myhashs]

tried with old version and still have same error i tired 4.0.1 also delete hashcat folder and installed 4.01 but have same problem

[s3inlc]

ok, that's the reason why it's not working. You should only put hashcat as the binary name, without any version number. Because the binary is called hashcat64.bin, so you should only provide the basename without the 32/64-bit and the ending.

[myhashs]

Stopped: Tue Jul 10 10:02:47 2018

Getting chunk... Progress: 0.33% | Speed:64.31KH/s | Cracks:0 | Accepted:0 | Zapped:0 | Queue:1 Progress: 0.76% | Speed:63.48KH/s | Cracks:0 | Accepted:0 | Zapped:0 | Queue:1 Progress: 1.20% | Speed:63.63KH/s | Cracks:0 | Accepted:0 | Zapped:0 | Queue:1 Progress: 1.61% | Speed:62.83KH/s | Cracks:0 | Accepted:0 | Zapped:0 | Queue:1

seems my GPU is not runned pls help me solver this

[s3inlc]

Why do you say your GPU is not running? There seems to be some work done, to see if there is a problem I would need more information on the task and hardware you have.

[myhashs]

Stopped: Tue Jul 10 10:02:47 2018

Getting chunk... Progress: 0.33% | Speed:64.31KH/s | Cracks:0 | Accepted:0 | Zapped:0 | Queue:1 Progress: 0.76% | Speed:63.48KH/s | Cracks:0 | Accepted:0 | Zapped:0 | Queue:1 Progress: 1.20% | Speed:63.63KH/s | Cracks:0 | Accepted:0 | Zapped:0 | Queue:1 Progress: 1.61% | Speed:62.83KH/s | Cracks:0 | Accepted:0 | Zapped:0 | Queue:1

Graphic cards:	Intel Corporation HD Graphics 610 (rev 04)NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1)NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1)NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1)NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1)

[myhashs]

• 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
• Device #5: Not a native Intel OpenCL runtime. Expect massive speed loss. You can use --force to override, but do not report related errors.

Dictionary cache built:

• Filename..: /home/fenix/hashtopussy/files/words1.txt
• Passwords.: 80511
• Bytes.....: 883162
• Keyspace..: 80511
• Runtime...: 0 secs

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

[s3inlc]

Let me know what kind of task what you're trying to run and on which algorithm.

[myhashs]

i got 6000 sha256unix passwords and wanna try it with 80k passwords

[s3inlc]

I definitely would recommend to not use the Intel card (so just make sure it only uses the other GTX GPUs). But I don't see a problem with the task here, 6000 sha256unix is pretty a hard list and the algorithm is not that fast, so the speed you sent above looks not that bad in my opinion.

[myhashs]

how to set it up useing only gpu ?

[s3inlc]

Run hashcat64.bin -I on the agent and it will list you all the devices and their according numbers. And with specifying the agent specific parameters you can then set with the -d flag which devices should be used. E.g. -d 2,3,4

[myhashs]

agent details

Extra parameters:

this one ?

[s3inlc]

yes

[myhashs]

so 64kh/s is is normal speed for my sha256unix on 4x1080 ?

[s3inlc]

Depends on the rounds of the hashes. The best way to find out if it's an appropriate speed would be to quickly start the task manually on the agent and look which speed you get there.

Otherwise it's also possible that just your benchmark result was not that good and therefore the chunks are too small. But generally attacking large lists with hard hashes with small wordlists is difficult to run well.

[myhashs]

i just checked google 1 1080 like mine must to get 380kh/s speed i have only 64kh/s on 4 gpu

there is something wrong bro :(

[s3inlc]

You cannot compare with the default benchmark from hashcat because it might not be the same rounds number for the hashes, you need to compare with running an actual task with your hashes.

And as I said, it might also be the reason because the chunks are too small to fully use the GPUs.

[myhashs]

what chunks parameters need to use bro tell me pls and do i need use bigger wordlist ?

[s3inlc]

Have you checked what round cost your hashes do have? Did you run the same task manually once on your agent and what the speed is there? What kind of benchmark did you use and what was the result? What is the length of the chunk for the one which was issued to the agent?

[myhashs]

7500 rounds sha256unix have like i known no i didnot run it manually i used standart 600

[s3inlc]

Ok, so 7500 is 50% than the default rounds (which are also used to run the hashcat benchmark), so this definitely also has an effect on speed. Please run it manually for a few seconds and take a look at the speed, this helps a lot to identify the reason. I didn't meant the time length of a chunk, please have a look at the chunk information itself at the bottom what is given as Length of the chunk.

[myhashs]

give me commond line bro to run it manually pls

[s3inlc]

Just run what you configured as task in Hashtopolis and just put the hashlist file where you put #HL#.

[myhashs]

ok wait iam doing bench now

[myhashs]

Hashmode: 7400 - sha256crypt $5$, SHA256 (Unix)

Speed.Dev.#1.....: 353.2 kH/s (43.83ms) Speed.Dev.#2.....: 364.7 kH/s (42.32ms) Speed.Dev.#3.....: 362.0 kH/s (42.67ms) Speed.Dev.#4.....: 356.7 kH/s (43.26ms) Speed.Dev.#*.....: 1436.7 kH/s

[myhashs]

so i to use something wrong to get only 64kh/s on hastopolis lol :)

[s3inlc]

Again, as I said, Hashcat is not benchmarking with the same cost than the hashes you are trying to recover. Also the benchmark results are the ideal performance and most often are not achieved by real tasks.

Please run the specific attack you entered in the Hashtopolis task manually to compare.

[myhashs]

Session..........: hashcat Status...........: Running Hash.Type........: sha256crypt $5$, SHA256 (Unix) Hash.Target......: hash.txt Time.Started.....: Tue Jul 10 11:28:59 2018 (19 secs) Time.Estimated...: Tue Jul 10 12:28:33 2018 (59 mins, 15 secs) Guess.Base.......: File (words1.txt) Guess.Queue......: 1/1 (100.00%) Speed.Dev.#1.....: 28399 H/s (5.84ms) Speed.Dev.#2.....: 29187 H/s (5.71ms) Speed.Dev.#3.....: 33652 H/s (4.89ms) Speed.Dev.#4.....: 32150 H/s (5.12ms) Speed.Dev.#*.....: 123.4 kH/s Recovered........: 0/5477 (0.00%) Digests, 0/5477 (0.00%) Salts Recovered/Time...: CUR:N/A,N/A,N/A AVG:0,0,0 (Min,Hour,Day) Progress.........: 2214050/440958747 (0.50%) Rejected.........: 0/2214050 (0.00%) Restore.Point....: 0/80511 (0.00%) Candidates.#1....: 4936 -> Cohoe1 Candidates.#2....: cohurype -> k151790 Candidates.#3....: qssnvyng -> zzzzzzzz77 Candidates.#4....: k1650s -> qss987 HWMon.Dev.#1.....: Temp: 64c Fan: 41% Util: 98% Core:1822MHz Mem:4513MHz Bus:1 HWMon.Dev.#2.....: Temp: 48c Fan: 30% Util: 99% Core:1911MHz Mem:4513MHz Bus:1 HWMon.Dev.#3.....: Temp: 55c Fan: 34% Util: 95% Core:1885MHz Mem:4513MHz Bus:1 HWMon.Dev.#4.....: Temp: 48c Fan: 30% Util: 97% Core:1860MHz Mem:4513MHz Bus:1

[s3inlc]

You need to run it with hashcat, not hashtopolis.

-> ./hashcat64.exe -a 0 -m 7400 hash.txt words1.txt

[myhashs]

i did it check up message i change it

[s3inlc]

Ok, so the difference is not that big anymore. I guess the main reason for the speed drop is that the chunk is too small to fully use the GPUs potential when distributing it.

So what is the benchmark result shown for the agent?

[myhashs]

Hashmode: 7400 - sha256crypt $5$, SHA256 (Unix)

Speed.Dev.#1.....: 353.2 kH/s (43.83ms) Speed.Dev.#2.....: 364.7 kH/s (42.32ms) Speed.Dev.#3.....: 362.0 kH/s (42.67ms) Speed.Dev.#4.....: 356.7 kH/s (43.26ms) Speed.Dev.#*.....: 1436.7 kH/s

[s3inlc]

No no, I mean the benchmark result from Hashtopolis, which is shown on the assigned agent in the task details.

[myhashs]

Getting chunk... Progress: 0.33% | Speed:64.78KH/s | Cracks:0 | Accepted:0 | Zapped:0 | Queue:1 Progress: 0.77% | Speed:64.36KH/s | Cracks:0 | Accepted:0 | Zapped:0 | Queue:1 Progress: 1.20% | Speed:64.22KH/s | Cracks:0 | Accepted:0 | Zapped:0 | Queue:1

2 times lower

[s3inlc]

That's not the benchmark result from hashtopolis, that is the actual run speed..

I need this one:

[winxp5421]

Closing this issue due to inactivity. If you have any other issues please reopen or create a new issue ticket