Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Random generated rules are invalid rules (Due to non-ASCII Characters?) #3413

Open
OfficiallyCrazy opened this issue Aug 4, 2022 · 1 comment
Labels

Comments

@OfficiallyCrazy
Copy link

OfficiallyCrazy commented Aug 4, 2022

Describe the bug
When randomly generated rules are created and --debug-mode 1 is used, the output has invalid rules.

To Reproduce
Hashcat version: v6.2.5
Operating System: Windows 11
Terminal : CMD

  • Code used to create rules: hashcat -a 0 -m 0 -O --potfile-disable --debug-mode 1 --debug-file WOW.debug -g 1000 --generate-rules-seed 106406 --generate-rules-func-max 5 -o WOW.Cracked Hashes\WOW Wordlist.txt --loopback
  • Code used to run the rules: hashcat -a 0 -m 0 --potfile-disable Hashes\WOW Wordlist.txt -r WOW.debug -o test1.txt

Expected behavior
Since the randomly generated rule was present in the WOW.debug. This means that the word was modified given the rule. (I have tested this with the )
I expected all randomly generated present in the debug file to be valid rules

Hardware/Compute device (please complete the following information):

  • Compute device name: [e.g. RTX2080Ti]
  • OpenCL/CUDA driver name: [e.g. NVIDIA DRIVER]
  • OpenCL/CUDA driver version: [e.g. 465.21]
  • OpenCL/CUDA driver source: [e.g. runtime installer/.exe installer]

Hashcat version (please complete the following information):

  • OS: Windows 11
  • Version: v 6.2.0

Diagnostic output compute devices:
Skipping invalid or unsupported rule in file WOW.debug on line 7: t 3 O

Post hashcat -I output

hiprtcAddNameExpression is missing from HIPRTC shared library.

OpenCL Info:

OpenCL Platform ID #1
Vendor..: Advanced Micro Devices, Inc.
Name....: AMD Accelerated Parallel Processing
Version.: OpenCL 2.1 AMD-APP (3444.0)

Backend Device ID #1
Type...........: GPU
Vendor.ID......: 1
Vendor.........: Advanced Micro Devices, Inc.
Name...........: AMD Radeon RX 6600
Version........: OpenCL 2.0 AMD-APP (3444.0)
Processor(s)...: 14
Clock..........: 2044
Memory.Total...: 8176 MB (limited to 6732 MB allocatable in one block)
Memory.Free....: 8064 MB
OpenCL.Version.: OpenCL C 2.0
Driver.Version.: 3444.0 (PAL,LC)
PCI.Addr.BDF...: 08:00.0

Backend Device ID #2
Type...........: GPU
Vendor.ID......: 1
Vendor.........: Advanced Micro Devices, Inc.
Name...........: AMD Radeon RX 6600 XT
Version........: OpenCL 2.0 AMD-APP (3444.0)
Processor(s)...: 16
Clock..........: 2413
Memory.Total...: 8176 MB (limited to 6732 MB allocatable in one block)
Memory.Free....: 8064 MB
OpenCL.Version.: OpenCL C 2.0
Driver.Version.: 3444.0 (PAL,LC)
PCI.Addr.BDF...: 03:00.0

Additional context
From what I understood. Some rules being rejected are those which contain non ASCII characters.
When I sorted the most common rules from the debug file, the 7th line (7th most common rule) is maked as invalid.

On the terminal the invalid rule looks like this: t 3 O
On the WOW.debug file: the rule looks like this: t 3ÿO

Please note the example provided above is only one example.

@jsteube
Copy link
Member

jsteube commented Aug 4, 2022

It seems the problem is in the debugging output;. Could you please provide a single hash file and a single wordlist file that enables us to reproduce the problem at that point where the problem is generated initially.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants