You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reading all rules in a directory was a recent feature request in #1182 . New users may try this. If they do, instead of rejecting the attempt early, hashcat goes through the full setup phase (hash loading, hardware initialization, potfile processing, etc.) and then pauses for a very long time at "Generated bitmap tables":
It appears that hashcat may be trying to parse the directory as a ruleset? Not sure. If so, this could have weird side effects we should avoid.
Suggested solution: check if -r parameter is a directory, abort early, and suggest to the user the alternative that @jsteube suggested in #1182, but phrased to be platform-independent - someting like "Rules cannot be loaded from a directory. Concatenate your rules into a single file instead". This could head off a FAQ.
The text was updated successfully, but these errors were encountered:
I discovered this issue while researching #1185.
Reading all rules in a directory was a recent feature request in #1182 . New users may try this. If they do, instead of rejecting the attempt early, hashcat goes through the full setup phase (hash loading, hardware initialization, potfile processing, etc.) and then pauses for a very long time at "Generated bitmap tables":
It appears that hashcat may be trying to parse the directory as a ruleset? Not sure. If so, this could have weird side effects we should avoid.
Suggested solution: check if -r parameter is a directory, abort early, and suggest to the user the alternative that @jsteube suggested in #1182, but phrased to be platform-independent - someting like "Rules cannot be loaded from a directory. Concatenate your rules into a single file instead". This could head off a FAQ.
The text was updated successfully, but these errors were encountered: