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

Annoying errors in hashcat-git #3991

Open
mohemiv opened this issue Apr 17, 2024 · 0 comments
Open

Annoying errors in hashcat-git #3991

mohemiv opened this issue Apr 17, 2024 · 0 comments

Comments

@mohemiv
Copy link
Contributor

mohemiv commented Apr 17, 2024

Hello there,

I have noticed that hashcat-git outputs quite a lof of annoying errors.

Error 1

$ hashcat
/hashcat -b
hashcat (v6.2.6-848-gc1a10518f+) starting in benchmark mode

Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.

The device #14 specifically listed was skipped because it is an alias of device #1

The device #15 specifically listed was skipped because it is an alias of device #2

The device #16 specifically listed was skipped because it is an alias of device #3

The device #17 specifically listed was skipped because it is an alias of device #4

The device #18 specifically listed was skipped because it is an alias of device #5

The device #19 specifically listed was skipped because it is an alias of device #6

The device #20 specifically listed was skipped because it is an alias of device #7

The device #21 specifically listed was skipped because it is an alias of device #8

The device #22 specifically listed was skipped because it is an alias of device #9

The device #23 specifically listed was skipped because it is an alias of device #10

The device #24 specifically listed was skipped because it is an alias of device #11

The device #25 specifically listed was skipped because it is an alias of device #12

CUDA API (CUDA 12.4)
====================
* Device #1: NVIDIA GeForce RTX 4090, 23816/24210 MB, 128MCU
* Device #2: NVIDIA GeForce RTX 4090, 23816/24210 MB, 128MCU
* Device #3: NVIDIA GeForce RTX 4090, 23816/24210 MB, 128MCU
* Device #4: NVIDIA GeForce RTX 4090, 23816/24210 MB, 128MCU
* Device #5: NVIDIA GeForce RTX 4090, 23816/24210 MB, 128MCU
* Device #6: NVIDIA GeForce RTX 4090, 23816/24210 MB, 128MCU
* Device #7: NVIDIA GeForce RTX 4090, 23816/24210 MB, 128MCU
* Device #8: NVIDIA GeForce RTX 4090, 23816/24210 MB, 128MCU
* Device #9: NVIDIA GeForce RTX 4090, 23816/24210 MB, 128MCU
* Device #10: NVIDIA GeForce RTX 4090, 23816/24210 MB, 128MCU
* Device #11: NVIDIA GeForce RTX 4090, 23816/24210 MB, 128MCU
* Device #12: NVIDIA GeForce RTX 4090, 23816/24210 MB, 128MCU

OpenCL API (OpenCL 2.1 LINUX) - Platform #1 [Intel(R) Corporation]
==================================================================
* Device #13: Intel(R) Xeon(R) Gold 6246R CPU @ 3.40GHz, skipped

OpenCL API (OpenCL 3.0 CUDA 12.4.125) - Platform #2 [NVIDIA Corporation]
========================================================================
* Device #14: NVIDIA GeForce RTX 4090, skipped
* Device #15: NVIDIA GeForce RTX 4090, skipped
* Device #16: NVIDIA GeForce RTX 4090, skipped
* Device #17: NVIDIA GeForce RTX 4090, skipped
* Device #18: NVIDIA GeForce RTX 4090, skipped
* Device #19: NVIDIA GeForce RTX 4090, skipped
* Device #20: NVIDIA GeForce RTX 4090, skipped
* Device #21: NVIDIA GeForce RTX 4090, skipped
* Device #22: NVIDIA GeForce RTX 4090, skipped
* Device #23: NVIDIA GeForce RTX 4090, skipped
* Device #24: NVIDIA GeForce RTX 4090, skipped
* Device #25: NVIDIA GeForce RTX 4090, skipped

Benchmark relevant options:
===========================
* --backend-devices-virtual=1
* --optimized-kernel-enable

-------------------
* Hash-Mode 0 (MD5)
-------------------
[REDACTED]

There is no need to show me every run that devices 14-25 were skipped.

See also: #3961

Error 2

$ hashcat -a 13100 ./user.txt --show --username
Mixing --show with --username or --dynamic-x can cause exponential delay in output.

admin:b4b9b02e6f09a9bd760f388b67351e2b

There is no need for this message.

The --username option in Hashcat was designed to improve user experience. Now, each time --username is used, Hashcat outputs a red text, treating --username as unfavorably as --force, for example.

I have not noticed any significant delays in output when using the --username option.

See also: #3655 #3988

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

No branches or pull requests

1 participant