02-21-2019, 02:52 PM
Every user having their own hashcat is the workaround we use now, but this is not our preferred solution, for 2 reasons:
1. It requires multiple users to keep their hashcat up-to-date, and I don't expect that to go too well.
2. We currently have a bash script that people use, which does all kinds of masks and other smart tricks (don't know the specifics, it's not mine), running a bunch of hashcat commands in sequence. This would also require everyone having their own version of this script, which will have the same problem as 1.
Hashcat is installed by downloading and extracting the zip, and putting it in /opt/
To explain our workflow some more, everyone has their own user on the system, and they might log in at the same time. only 1 user running hashcat at the same time is exactly what we're trying to avoid.
These users login, start a screen session, run the script, and basically wait for results.
I hope this helps explain my situation, and thanks in advance for the help!
1. It requires multiple users to keep their hashcat up-to-date, and I don't expect that to go too well.
2. We currently have a bash script that people use, which does all kinds of masks and other smart tricks (don't know the specifics, it's not mine), running a bunch of hashcat commands in sequence. This would also require everyone having their own version of this script, which will have the same problem as 1.
Hashcat is installed by downloading and extracting the zip, and putting it in /opt/
To explain our workflow some more, everyone has their own user on the system, and they might log in at the same time. only 1 user running hashcat at the same time is exactly what we're trying to avoid.
These users login, start a screen session, run the script, and basically wait for results.
I hope this helps explain my situation, and thanks in advance for the help!