There should be hooks which allow notifications on different channels like Mattermost, Email etc. on some actions.
It should be configurable for different kinds of events to have different notifications.

update the pre-tasks page and functionality

Check what changes are required to the server to be able to handle the new hashcat hccapx format.

See here: https://hashcat.net/forum/thread-6273.html

See output

Hashlist contained 2 hashes, 2 hashes were cracked in the chunk.
When queried for work the server is responding with same chunk when it should in fact with more no tasks or next task rather than chunk from same task.

{"action":"solve","token":"nqRsKOJbj3","chunk":104,"keyspaceProgress":0,"progres
s":114200000,"total":200000000,"speed":7230294,"state":5,"cracks":["02c879de651d
eb8a1e146d87287dd568:cba:32165487","9a361ed860ec2617da5af72079594a21:abc:1234567
8"]}
Attack finished
{"action":"solve","response":"SUCCESS","cracked":2,"skipped":0,"zaps":[]}
Progress:114200000/200000000 (57.1%)
Total Speed:7230294
Uploaded 2 cracks, server accepted 2
Finished last chunk
{"action":"chunk","response":"SUCCESS","status":"OK","chunk":104,"skip":0,"lengt
h":100000}

In some cases the API checks the token of the agent multiple times or loads the agent twice. This should get cached in some way to reduce MySQL queries

If a task is finished because all hashes are cracked, it's still shown on the list as being active on a chunk.

submission of salted hash founds from the agent doesn't seem to work

On the hashes.php view the hashes of hashlists which are salted, are only displayed without salt.

Check the Utils class if still all functions there are required and do make sense.
Also add some Documentation to the functions.

Have a Notes field to paste notes on the hashlist,
Also, include Previous tasks name's that have finished completely ( even if they are removed from tasks.php)

Superhashlists do not show founds at all

Fatal error: Uncaught exception 'PDOException'.....

Implement the functions which are available on the Config page below the config fields.

Aborting a chunk doesn't work as the chunk state gets overwritten before it gets checked

As we get a new feature in Hashcat for benchmarking tasks (--progress-only) the creation of the chunks and how the benchmark is stored need to be changed.

This affects quite some locations in the source code and it should be carefully be checked where these are.

• Fix sql queries
• Update template and remove the not used fields

Update the 'chunk' action for the connection Server <-> Client

Due to the way how the benchmarking is done, there is a special case where the benchmarking can result in chunks which are not all equally same size (in calculation time).

Because on salted hashes the benchmarking is done on a single hash, if you use hashes with weights (like for example in bcrypt) and the hashes in the list do not all have the same weight, the result will not reflect the average for all hashes, but will be calculated from the weight of the first hash in the list.

• Include the creation of new agents into the agents.php file
• Extend the AgentHandler for handling new agents
• Complete the agent detail view and implement the new SQL queries

{"action":"solve","token":"xx15Dkz4iE","chunk":93,"keyspaceProgress":0,"progress
":114200000,"total":200000000,"speed":7566838,"state":5,"cracks":["02c879de651de
b8a1e146d87287dd568:cba:32165487","9a361ed860ec2617da5af72079594a21:abc:12345678
"]}
{"action":"solve","response":"SUCCESS","cracked":0,"skipped":0,"zaps":[]}
Progress:114200000/200000000 (57.1%)
Total Speed:7566838

Uploaded 2 cracks, server accepted 0

The server is not accepting cracked salted hashes

• Fix the sql queries
• Add better error messages

Update the 'solve' action for the connection Server <-> Client

Fix the sql queries on the chunks page.

Copying a task with the 'Copy' button on an existing task is not working. The values don't get copied into the form for creating a new task.

See https://alpha.hashes.org/src/tasks.php?id=57:

• All chunks are shown active, even there was no activity over long time or even if they are finished.
• The agent is also shown active all the time
• All the dispatches chunks show N/A as agent
• Chunks are shown twice as soon as a second agent is assigned to the same task
• Speeds shown on the agents are not correct (if there is more than one agent, the same speed is shown for both)
• Time spent on the task on the assigned agents is always 0
• Clicking on 'show all assignments' results in an error

When a chunk gets resized because it gets assigned to another agent, it should check if it resizes a chunk to length 0 and should delete it then. Otherwise there is a lot of trouble later.

The config page should display some information about every config setting and provide a name instead of just the string used in the code.
It would be nice to also have a check, that checks for every item that the corresponding value is allowed.

Allow in the installation procedure to enter a port if a non-standard MySQL port should be used to connect.

Scroll down, basically while the agent was running a task it was unassigned. The server responds with

{"action":"chunk","response":"ERROR","message":"You are not assigned to this task!"}

Which is correct, however when another part is uploaded the server seems to accept it

{"action":"solve","token":"nqRsKOJbj3","chunk":138,"keyspaceProgress":34,"progre
ss":29150750,"total":29150750,"speed":487,"state":4,"cracks":[]}
{"action":"solve","response":"SUCCESS","cracked":0,"skipped":0,"zaps":[]}
Progress:29150750/29150750 (100%)
Total Speed:487
Finished last chunk
Getting task

Then when a task is subsequently requested the server gives the client a task when it isn't suppose to

C:\Users\blazer\Documents\hashtopussy-agent\csharp\hashtopussy\bin\x64\Release\h
ashcat\hashcat64.exe -w 2 --gpu-temp-disable -d 3 --hash-type=0 "C:\Users\blaze
r\Documents\hashtopussy-agent\csharp\hashtopussy\bin\x64\Release\hashlists\21"
-a 3 ?a?a?a?a?a?a?a --outfile-check-dir="C:\Users\blazer\Documents\hashtopussy-a
gent\csharp\hashtopussy\bin\x64\Release\hashlists\zaps21" --potfile-disable --q
uiet --restore-disable --session=hashtopus --status --machine-readable --status-
timer=5 --outfile-check-timer=5 --remove --remove-timer=5 --separator=: --skip=3
3 --limit=1
Upload queue 1
{"action":"solve","token":"nqRsKOJbj3","chunk":138,"keyspaceProgress":33,"progre
ss":28293375,"total":28293375,"speed":635,"state":4,"cracks":[]}
{"action":"solve","response":"SUCCESS","cracked":0,"skipped":0,"zaps":[]}
Progress:28293375/28293375 (100%)
Total Speed:635
Finished last chunk
Writing Lines:
STATUS 4 SPEED 487 1 EXEC_RUNTIME 0.070367 CURKU
34 PROGRESS 29150750 29150750 RECHASH 0 879
RECSALT 0 1
Finished write:
Attack finished
{"action":"chunk","response":"ERROR","message":"You are not assigned to this tas
k!"}
ERROR
You are not assigned to this task!
Upload queue 1
{"action":"solve","token":"nqRsKOJbj3","chunk":138,"keyspaceProgress":34,"progre
ss":29150750,"total":29150750,"speed":487,"state":4,"cracks":[]}
{"action":"solve","response":"SUCCESS","cracked":0,"skipped":0,"zaps":[]}
Progress:29150750/29150750 (100%)
Total Speed:487
Finished last chunk
Getting task
{"action":"task","response":"SUCCESS","task":"72","wait":"30","attackcmd":"#HL#
-a 3 ?a?a?a?a?a?a?a","cmdpars":"-w 2 --gpu-temp-disable -d 3 --hash-type=0","has
hlist":"21","bench":"new","statustimer":"5","files":[]}
Hashlist for this task already exists, skiping download
{"action":"task","response":"SUCCESS","status":"benchmark"}

• Change all DB requests in files.php to the new DBA
• Put the 'action' requests into a new handler
• Update it that we get a view of two lists with files (one for the wordlists and one for the rules)

Ability to rename files in both Rules and wordlists sections of files.php

update superhashlist page and the functionality

Put all the templates of the agent details (templates/agents/detail/*) into one templating file and name it templates/agents/detail.template.html.

Update the 'keyspace' action for the connection Server <-> Client

Update the supertasks page and functionality

Needs work

• agents.php toggle active produces an error

• agents.php deletion not working

• newuser.php Creating a new user fails (object not found)

• users.php Deletion of user produces error

• file size determination on create wordlists does not work

• import ist not listing files in directory

Not Tested

• upload hashes from "Import" on files.php?view=rules, files.php?view=wordlists, and hashlist.php

• Import hashes from "Import" on hashlist.php?newtrue, superhashlists.php

• Agents.php entirely

• config.php Rebuild chunk cache, Rescan global files, Clear all # 18

• URL download on hashlist.php

• Client related things on tasks.php?idXX

• chunks.php

Tested and Working as of 12/2/16

• Tasks.php?

• supertasks.php?create=true

• users.php & users.php?id=1

• logout.php

• hashtypes.php

• account.php

• hashcat.php?new=true

• tasks.php?new=true

• superhashlists.php?new=true

Ideally, we would have a reusable script to fill the DB with some example data. This would make testing easier.

After we are ready for a beta release everyone needs to read through the help doc. So much has changed in this repo I simply do not have enough information to modify the entire document accurately. If you feel something needs to change place notes in this section.

Agent sections! If you create an agent get with @winxp5421 he will write a help section and/or assist users with troubleshooting.

The templating has some problems with rendering stuff like:

[[Util::shortenstring([[gpu]], 20)]]
[[date([[config.getVal('timefmt')]], [[set.getVal('agent').getLastTime()]])]]

This should be fixed somewhere in Statement.class.php

Modify the Supertasks lists to act more like Pre-configured tasks by including a supertasks list section in hashlists.php?id=XX instead of supertasks.php being the only place to issue work from.

Also in supertasks.php the copy button should not say copy it should be "create" or similar word as copy can be confusing when you are trying to issue work

Create a Collapsible/ Expandable ( or similar organizational UI) for Supertasks within tasks.php this would when collapsed allow grouping of tasks within a Supertask to be condensed into a single "Task" and when expanded to see each task within that Supertask. Visual representation http://prntscr.com/d1sx5a

Make Hashtype configuration that it can be set if the hash contains a salt or not, so this has not to be selected when adding a hashlist.

If a Pre-Configured task is deleted from preconf.php while it is still in a Supertasks list the user should be warned if they really want to remove it from both.

First login always gives 404 issue and directs user to https://alpha.hashes.org/src/false
Click back and login again, even with blank pw and it should work.

Make it possible that clients can submit both types of benchmarks and the server calculates the chunk length based on the given result.

This is required to avoid problems with transactions and also reduces the number of connections to the MySQL server.

Instead of just prefixing (copy) (copy), perhaps use something like copy1, copy2 copy3. or perhaps _X_copy, something to keep the names from getting extremely long.

A agent connecting to the server doesn't get automatically to a task which has priority>0.
It could be that the logic getting the task which should be run next by the agent, doesn't get a correct result.

Length var for tasks sometimes sent as int sometimes as string (depends whether the job already existed)

{"action":"task","response":"SUCCESS","status":"OK","chunk":"87","skip":"0","length":13762560}
{"action":"task","response":"SUCCESS","status":"OK","chunk":"87","skip":"0","length":"13762560"}

Update the 'task' action for the connection Server <-> Client

Update the 'bench' action for the connection Server <-> Client