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
As the title says, the "Input Queue" status line is replaced with "Input Charset" when the mask has a custom charset definition even if it's being read from file.
Example: create a file with the following lines and use the file as an input for a mask attack.:
Without the "input queue" status, it's difficult to tell your progress into the mask file. You can manually find your position by searching your mask file for the charsets and mask, but it can get tedious. The above example is pretty short, but hopefully it illustrates the issue.
In lieu of a pull request, I suggest changing these lines to:
case INPUT_MODE_MASK:
case INPUT_MODE_MASK_CS:
event_log_info (hashcat_ctx,
"Input.Queue......: %d/%d (%.02f%%)",
hashcat_status->input_base_offset,
hashcat_status->input_base_count,
hashcat_status->input_base_percent);
break;
(Added the case label for INPUT_MODE_MASK_CS)
P.S. Sorry for opening so many issues today. Keep up the good work!
The text was updated successfully, but these errors were encountered:
As the title says, the "Input Queue" status line is replaced with "Input Charset" when the mask has a custom charset definition even if it's being read from file.
Example: create a file with the following lines and use the file as an input for a mask attack.:
Without the "input queue" status, it's difficult to tell your progress into the mask file. You can manually find your position by searching your mask file for the charsets and mask, but it can get tedious. The above example is pretty short, but hopefully it illustrates the issue.
In lieu of a pull request, I suggest changing these lines to:
(Added the case label for
INPUT_MODE_MASK_CS
)P.S. Sorry for opening so many issues today. Keep up the good work!
The text was updated successfully, but these errors were encountered: