jessevz
jessevz
made a cache for the benchmarks so that benchmarks can be reused and the benchmark proces can be skipped when the benchmark has already been cached. Key components: - Added...
Added frontend components for benchmark cache: https://github.com/hashtopolis/server/pull/955
### Description Currently the project only makes use of HTException as a very general exception for all error cases. This makes it challenging to handle different errors appropriately. Especially if...
fixes #725 The current code didn't work in case of an ipv6 address. This is because the host name got parsed by using strpos($hostname, ":"). this goes perfectly fine for...
### Description Currently in the new UI, at the hashlist page, it contains a sortable percentage with the amount of cracks. Since this is sortable, it is not really possible...
### Version Information 0.14.4-dev ### Hashcat _No response_ ### Description in the task detail page (ex: http://127.0.0.1:4200/#/tasks/show-tasks/41/edit). The user can assign agents to the task, it is very easy to...
### Version Information 0.14.4-dev ### Hashcat _No response_ ### Description when visiting the tasks detail page (ex: http://127.0.0.1:4200/#/tasks/show-tasks/171/edit/), there is a chunk table which shows the chunks related to this...
### Description In the new webUI, when the JWT token has been expired, the frontend becomes unresponsive. Clicking on new pages wont do anything. You have to refresh the page...
### Description Currently the new UI and API are both missing the agenterrors - [x] Create endpoint for agentErrors - [ ] Create UI component to show agentErrors
### Description Currently we do a CORS hack by just allowing everything, but this should be properly implemented and validated. The easiest way to implement would probably to let the...