Version Information
rc1
Hashcat
No response
Description
This affects both the current frontend and the new API, but it only makes sense to fix it on the new API as it's a rare case to occur.
When requesting all the cracks of a task, it determines these by getting all chunk IDs and then looking up the hashes cracked within these chunks. This can cause limits for the SQL server when the number of chunkIds used in the query grows very large. To solve this, the lookup should be made in one query (instead of two) with a join.
Version Information
rc1
Hashcat
No response
Description
This affects both the current frontend and the new API, but it only makes sense to fix it on the new API as it's a rare case to occur.
When requesting all the cracks of a task, it determines these by getting all chunk IDs and then looking up the hashes cracked within these chunks. This can cause limits for the SQL server when the number of chunkIds used in the query grows very large. To solve this, the lookup should be made in one query (instead of two) with a join.