hashcat Forum
Which is the best cracking mode? - Printable Version

+- hashcat Forum (https://hashcat.net/forum)
+-- Forum: Support (https://hashcat.net/forum/forum-3.html)
+--- Forum: hashcat (https://hashcat.net/forum/forum-45.html)
+--- Thread: Which is the best cracking mode? (/thread-11564.html)

Pages: 1 2


RE: Which is the best cracking mode? - Snoopy - 08-28-2023

well this should not be really the problem, unless you are using a real old/low spec graphiccard or somthing like a laptop (thats why i asked for output of hashcat -I , but never the less you could try the following, use your CPU instead of GPU by adding the following options (as normally there is more RAM built in than graphics RAM)

-D1 -d1

regarding rules, these are applied directly on your graphicscard so this should also be no problem even when using more rules


RE: Which is the best cracking mode? - ly88888 - 08-29-2023

(08-28-2023, 01:58 PM)Snoopy Wrote: well this should not be really the problem, unless you are using a real old/low spec graphiccard or somthing like a laptop (thats why i asked for output of hashcat -I , but never the less you could try the following, use your CPU instead of GPU by adding the following options (as normally there is more RAM built in than graphics RAM)

-D1 -d1

regarding rules, these are applied directly on your graphicscard so this should also be no problem even when using more rules

PS H:\Downloads\Compressed\hashcat-6.2.6+628\hashcat-6.2.6> ./hashcat -I
hashcat (v6.2.6-628-g76fae63be) starting in backend information mode

Support for HIPRTC was dropped by AMD Adrenalin Edition 22.7.1 and later.
This is not a hashcat problem.

For details please read: https://github.com/hashcat/hashcat/issues/3501

In order to make HIP work, you have two options:
- Install AMD Adrenalin version 22.5.1 EXACTLY
- Read the details from the above link for other workarounds

You can also just stick to OpenCL support.
To do this, just use --backend-ignore-hip option to ignore HIP.

CUDA Info:
==========

CUDA.Version.: 12.2

Backend Device ID #1 (Alias: #2)
  Name...........: NVIDIA GeForce RTX 2070 SUPER
  Processor(s)...: 40
  Clock..........: 1800
  Memory.Total...: 8191 MB
  Memory.Free....: 7137 MB
  Local.Memory...: 64 KB
  PCI.Addr.BDFe..: 0000:01:00.0

OpenCL Info:
============

OpenCL Platform ID #1
  Vendor..: NVIDIA Corporation
  Name....: NVIDIA CUDA
  Version.: OpenCL 3.0 CUDA 12.2.138

  Backend Device ID #2 (Alias: #1)
    Type...........: GPU
    Vendor.ID......: 32
    Vendor.........: NVIDIA Corporation
    Name...........: NVIDIA GeForce RTX 2070 SUPER
    Version........: OpenCL 3.0 CUDA
    Processor(s)...: 40
    Clock..........: 1800
    Memory.Total...: 8191 MB (limited to 2047 MB allocatable in one block)
    Memory.Free....: 8064 MB
    Local.Memory...: 48 KB
    OpenCL.Version.: OpenCL C 1.2
    Driver.Version.: 537.13
    PCI.Addr.BDF...: 01:00.0

PS H:\Downloads\Compressed\hashcat-6.2.6+628\hashcat-6.2.6>


————————————————————————————————————————————————————————


PS H:\Downloads\Compressed\hashcat-6.2.6+628\hashcat-6.2.6> ./hashcat -m 0 -b
hashcat (v6.2.6-628-g76fae63be) 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.

Support for HIPRTC was dropped by AMD Adrenalin Edition 22.7.1 and later.
This is not a hashcat problem.

For details please read: https://github.com/hashcat/hashcat/issues/3501

In order to make HIP work, you have two options:
- Install AMD Adrenalin version 22.5.1 EXACTLY
- Read the details from the above link for other workarounds

You can also just stick to OpenCL support.
To do this, just use --backend-ignore-hip option to ignore HIP.

* Device #1: WARNING! Kernel exec timeout is not disabled.
            This may cause "CL_OUT_OF_RESOURCES" or related errors.
            To disable the timeout, see: https://hashcat.net/q/timeoutpatch
* Device #2: WARNING! Kernel exec timeout is not disabled.
            This may cause "CL_OUT_OF_RESOURCES" or related errors.
            To disable the timeout, see: https://hashcat.net/q/timeoutpatch
CUDA API (CUDA 12.2)
====================
* Device #1: NVIDIA GeForce RTX 2070 SUPER, 7137/8191 MB, 40MCU

OpenCL API (OpenCL 3.0 CUDA 12.2.138) - Platform #1 [NVIDIA Corporation]
========================================================================
* Device #2: NVIDIA GeForce RTX 2070 SUPER, skipped

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

-------------------
* Hash-Mode 0 (MD5)
-------------------

Speed.#1.........: 33880.9 MH/s (77.64ms) @ Accel:128 Loops:1024 Thr:512 Vec:8

Started: Tue Aug 29 09:16:33 2023
Stopped: Tue Aug 29 09:16:50 2023
PS H:\Downloads\Compressed\hashcat-6.2.6+628\hashcat-6.2.6>

————————————————————————————————————————————————————————


Will stay at this stage for a long time
Candidates.#1....: [Copying]