03-31-2016, 06:45 PM
You don't really need to understand how hashcat calculates the base/mod loop sizes to use --keyspace. But if you want to understand, study https://github.com/hashcat/hashcat-utils...keyspace.c
There is no direct relationship between keyspace and runtime, and by that I mean it's impossible to determine runtime from keyspace alone. You need to have benchmarks for your hardware to know how much work you can do in a given period of time for each algorithm. Especially since you say you want to have a task run for a defined period of time, e.g. one hour. So you need to figure out how much work one node can do in one hour and use that to calculate your -s/-l offsets.
There is no direct relationship between keyspace and runtime, and by that I mean it's impossible to determine runtime from keyspace alone. You need to have benchmarks for your hardware to know how much work you can do in a given period of time for each algorithm. Especially since you say you want to have a task run for a defined period of time, e.g. one hour. So you need to figure out how much work one node can do in one hour and use that to calculate your -s/-l offsets.