12-09-2015, 05:23 AM
The reason why I suggested an internal search path is to help keep command lines sane.
Here's an example: I want to run a simple rule-based attack.
oclHashcat64 hashlist wordlist -r /usr/share/oclHashcat/rules/best64.rule
Versus:
oclHashcat64 hashlist wordlist -r best64.rule
And the reason why I suggested paths for rules, hcmask files, etc in the working directory are for similar reasons. If a user creates their own rules, hcmask files, etc., they need a logical place to put them. With the rest of their password cracking stuff makes sense. And similarly, you don't want to have to do this all the time:
oclHashcat64 hashlist wordlist -r ~/.hashcat/rules/my.rule
Instead, it would be much nicer if the user could simply do
oclHashcat64 hashlist wordlist -r my.rule
So having an internal search path that first checks ~/.hashcat then /usr/share/{hashcat,oclHashcat} for things would be really nice.
Here's an example: I want to run a simple rule-based attack.
oclHashcat64 hashlist wordlist -r /usr/share/oclHashcat/rules/best64.rule
Versus:
oclHashcat64 hashlist wordlist -r best64.rule
And the reason why I suggested paths for rules, hcmask files, etc in the working directory are for similar reasons. If a user creates their own rules, hcmask files, etc., they need a logical place to put them. With the rest of their password cracking stuff makes sense. And similarly, you don't want to have to do this all the time:
oclHashcat64 hashlist wordlist -r ~/.hashcat/rules/my.rule
Instead, it would be much nicer if the user could simply do
oclHashcat64 hashlist wordlist -r my.rule
So having an internal search path that first checks ~/.hashcat then /usr/share/{hashcat,oclHashcat} for things would be really nice.