The new Hashtopolis release contains various new features and enhancements:

Features

• The server saves the crackpos for hash founds given by hashcat.
  
• Trimming of chunks can be disabled so a chunk is always run fully again (or splitted if it is too large).
  
• Supertasks can now can be created by specifying a base command and iterate over a selection of files to be placed in the command.
  
• Notes can be added to hashlists.
  
• Added optional trace logging of actions from the client API to get more information in case of failures.
  
• Slow hashes are marked, so the client can decide if piping could make sense for this hash type.
  
• Agents can run health checks to determine if all agents are running correctly.
  

• Fixed GPU data graph when having multiple agents.
  
• Fixed assignment issue with subtasks of supertasks if they were in the same supertask.
  
• Fixed that cracker types cannot be deleted when there are supertasks using this type.
  

• Telegram notifications can now completely be configured via server config and also can be used through proxies.
  
• Peppers of Encryption.class.php and CSRF.class.php were moved out of the files to make updating easier.
  
• When importing supertasks it can be selected if they should use the optimized flag and which benchmark type should be used.
  
• Subtasks are only loaded when being viewed to speed up loading of the tasks page.
  
• Changed type of the hash column to TEXT to make sure to handle all the long hashes. It should not affect speed as long as there is not a multi-million hashlist.
  
• Preconfigured task attack commands can be edited after creation.
  
• If needed it can be set that the server should also distribute tasks with priority 0.
  

Please help for my problem.

1. I install Ubuntu 18.04.1 for server, and install all components from video instruction (Mysql, php, phpmyadmin) latest version.
Server UP and works.
2. Install client on rig 4-gpu AMD (Ubuntu 16.04.4 LTS)
3. Using any version hashcat 4.2.1 ; 4.2.0 ; 4.0.1  (hashcat works normal from download directory)
4. Create task -a 3 #HL# ?d?d?d?d?d?d?d?d (upload *.hccapx files) hachcat correct woks with this files if direct run.
4. Client get task and get error
debug :

Quote:Finished downloading file
{"action":"downloadBinary","type":"cracker","token":"Bq80ZjWMbh","binaryVersionId":1,"force":0}
{"action":"downloadBinary","response":"SUCCESS","url":"https:\/\/hashcat.net\/files\/hashcat-4.2.1.7z","name":"hashcat","executable":"hashcat.bin"}
Client already exists, skipping download
Getting chunk...
{"action":"getChunk","token":"Bq80ZjWMbh","taskId":42}
{"action":"getChunk","response":"SUCCESS","status":"keyspace_required"}
Server has requested the client measure the keyspace for this task
Using /home/user/hashtopussy/hashcat/1 as working directory
/home/user/hashtopussy/hashcat/1/hashcat64.bin   -p : --hash-type=2500  -a 3  ?d?d?d?d?d?d?d?d  --session=hashtopolis --keyspace --quiet
{"action":"sendKeyspace","token":"Bq80ZjWMbh","taskId":42,"keyspace":10000000}
Getting chunk...
{"action":"getChunk","token":"Bq80ZjWMbh","taskId":42}
{"action":"getChunk","response":"SUCCESS","status":"benchmark"}
Using /home/user/hashtopussy/files/ as working directory
/home/user/hashtopussy/hashcat/1/hashcat64.bin  -p : --hash-type=2500  -a 3 "/home/user/hashtopussy/hashlists/1" ?d?d?d?d?d?d?d?d  --restore-disable --potfile-disable  --machine-readable --session=hashtopolis --runtime=20
Server requested the client benchmark this task for 20 seconds
hashcat (v4.2.1) starting...









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

Applicable optimizers:
* Zero-Byte
* Single-Salt
* Brute-Force
* Slow-Hash-SIMD-LOOP

Minimum password length supported by kernel: 8
Maximum password length supported by kernel: 63

Watchdog: Temperature abort trigger set to 90c


Initialized device kernels and memory...

Benchmark was unsuccessful, check all files are present
root@rig-07:~/hashtopussy#

Quote:Getting task
{"action":"getTask","token":"Bq80ZjWMbh"}
{"action":"getTask","response":"SUCCESS","taskId":43,"attackcmd":"-a3 #HL# ?d?d?d?d?d?d?d?d","cmdpars":" -p : --hash-type=2500 ","hashlistId":1,"bench":20,"statustimer":5,"files":[],"crackerId":"1","benchType":"speed","hashlistAlias":"#HL#","keyspace":"0","usePrince":false,"enforcePipe":false}
Server has assigned client with Task:43, Cracker:1 and Hashlist:1
Downloading hashlist for this task, please wait...
{"action":"getHashlist","token":"Bq80ZjWMbh","hashlistId":1}
{"action":"getHashlist","response":"SUCCESS","url":"getHashlist.php?hashlists=1&token=Bq80ZjWMbh"}
Downloading from http://172.16.10.71/getHashlist.php?hash...Bq80ZjWMbh
Downloading 100% @ 230.21 KB/s
Finished downloading file
{"action":"downloadBinary","type":"cracker","token":"Bq80ZjWMbh","binaryVersionId":1,"force":0}
{"action":"downloadBinary","response":"SUCCESS","url":"https:\/\/hashcat.net\/files\/hashcat-4.2.1.7z","name":"hashcat","executable":"hashcat.bin"}
Client already exists, skipping download
Getting chunk...
{"action":"getChunk","token":"Bq80ZjWMbh","taskId":43}
{"action":"getChunk","response":"SUCCESS","status":"keyspace_required"}
Server has requested the client measure the keyspace for this task
Using /home/user/hashtopussy/hashcat/1 as working directory
/home/user/hashtopussy/hashcat/1/hashcat64.bin   -p : --hash-type=2500  -a3  ?d?d?d?d?d?d?d?d  --session=hashtopolis --keyspace --quiet
{"action":"sendKeyspace","token":"Bq80ZjWMbh","taskId":43,"keyspace":10000000}
Getting chunk...
{"action":"getChunk","token":"Bq80ZjWMbh","taskId":43}
{"action":"getChunk","response":"SUCCESS","status":"benchmark"}
Using /home/user/hashtopussy/files/ as working directory
/home/user/hashtopussy/hashcat/1/hashcat64.bin  -p : --hash-type=2500  -a3 "/home/user/hashtopussy/hashlists/1" ?d?d?d?d?d?d?d?d  --restore-disable --potfile-disable  --machine-readable --session=hashtopolis --progress-only
Server has requested the client perform a speed benchmark
hashcat (v4.2.1) starting in progress-only mode...


{"action":"sendBenchmark","token":"Bq80ZjWMbh","taskId":43,"type":"speed","result":"0:0"}
{"action":"sendBenchmark","response":"ERROR","message":"Invalid benchmark result!"}
ERROR
Invalid benchmark result!
Server rejected benchmark
Check the hashlist was downloaded correctly

Thanks for creating a forum for hashtop!

My question is that I'm looking to automate the upload and creation of hashlist. It would be nice during cracking competitions to send a hash list to the hashtop server and have it automagically upload said list into the hashlists tab with proper algo to be processed by the various tasks and supertasks set up. If this isn't something I can do natively with what's included with hashtop's setting/functionality is it something I could write up with a script?

So the end result could look like..... 
Send 100md5.txt to hashtop server
Hashtop reads in 100md5.txt and crates a md5 hashlist in the hashlists tab. 
Hashtop creates supertasks and tasks with various rules and attack modes to use against said hashlist. 
Tasks are sent out to agents for cracking. 

I'm mostly looking for some guidance/brainstorming on a way to accomplish this. Any help is appreciated. 

Providing users of this forum with appropriate and complete information in your initial post allows us to help you as quickly as possible.
This will save users from asking the same simple questions over and over. 


Not Providing adequate information will only increase the time it will take to solve the issue.

Long story short please give us the following information in your initial post:

• Current Server Version
  
• Current Client Version
  
• Hashcat Version
  
• Task command you are using eg. "#HL# wordlist.txt -r rulefile.rule"
  
• A detailed description of the problem you are experiencing
  
• Debug output from the client
  

Not respecting the rules can lead to instant ban or warnings, depending on the type of violation. The rules might be updated without explicitly notifying the user.

We are not a hacking site. Requests dealing with anything potentially illegal or questionable material will be dealt with accordingly.

• No double posting or unnecessary bumping.
  
• Do not post any personal details, always mask specific data (IPs, hashes, etc.).
  
• No hash cracking requests.
  
• No thread hijacking.
  
• Language is English, posts in other languages will be removed.
  
• Describe problems/questions appropriately and name your topic accordingly (also no caps lock texts).
  
• No advertising/selling/spam topics.
  
• No asking for leaks/hash lists.
  
• When having large text files (e.g. logs) don't put them in the text, use attachments instead.
  

Before you post a question, make sure you checked the following sources for information:

• Wiki on Github
  
• Issues on Github
  
• Changelog in case you are using an older version to make sure there was nothing changed regarding your question/issue.
  
• Frequent Problems to check if your issue is a common mistake or otherwise known one.