search

hashview / hashview-old

A web front-end for password cracking and analytics
http://www.hashview.io
GNU General Public License v3.0
620 stars 134 forks source link

Support for disable local agent computing #400

Open VlanOPing opened 6 years ago

VlanOPing commented 6 years ago

Hi,

My hashview server is installed on a VM without any hashcat capabilities : 0 GPU / 0 CPU

I have 2 remote agents working.

It would be great to add the option to assign work only on remote agent ( disable local agent ).

Actually, the remote agents are working on firsts chunks, the local agent fail to process all others.

i128 commented 6 years ago

I like this idea.

ccammilleri commented 6 years ago

as of right now the only reason why the main instance requires the local agent is due to keypace computing. @i128 with your upcoming changes to dynamic chunking, will keyspace be computed by hashcat still?

i128 commented 6 years ago

Dynamic chunking will still require keyspace calculations for tasks.and thus require hashcat to be installed. However, requiring hashcat to be installed does not mean the agent needs to be running. Although with dynamic chunking in place, people might want to keep the local agent anyways. Free CPU/GPU cycles.

GrepItAll commented 6 years ago

I'm a fan of this idea too. My current setup has a multi-GPU cracking machine acting as it's own controller/server, but this is an absolute pain as Linux doesn't play too nicely with multiple Nvidia cards. It would be great to move the controller/Hashview to a VM on an existing VM server and then deploy our GPU server as a Windows machine with the Hashview-agent, which would make it much more flexible in terms of driver/overclocking support.

In regards to the free CPU/GPU cycles, that's a fair point but being able to disable the local agent completely would be good if the VM is sharing CPU time with a bunch of other VMs.

coffeegist commented 4 years ago

Guessing this will never happen?