Only getting 1% of the hashrate of the benchmark
#2
The 7zip encryption mechanism has a variable "cost". The benchmark runs against a hash with a cost of 2^14 (16384 iterations), where your file has a cost of 2^19 (524,288 iterations). 

You can read more about the hash format here: https://github.com/philsmd/7z2hashcat

(04-11-2022, 03:31 PM)drtoctoc Wrote: I get 2KH/s on a hash attack vs more than 100KH/s on the benchmark. They're both running in the same mode -m 11600 -D 2



Benchmark results



Quote:***@***-MacBook-Pro hashcat % ./hashcat -b -m 11600 -O -D 2
hashcat (v6.2.5-383-g6509351dc) 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.

* Device #4: Apple's OpenCL drivers (GPU) are known to be unreliable.
             You have been warned.

* Device #5: Apple's OpenCL drivers (GPU) are known to be unreliable.
             You have been warned.

METAL API (Metal 261.13)
========================
* Device #1: AMD Radeon Pro 5500M, skipped
* Device #2: Intel(R) UHD Graphics 630, skipped

OpenCL API (OpenCL 1.2 (Feb 12 2022 01:56:27)) - Platform #1 [Apple]
====================================================================
* Device #3: Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz, skipped
* Device #4: Intel(R) UHD Graphics 630, 704/1536 MB (192 MB allocatable), 24MCU
* Device #5: AMD Radeon Pro 5500M Compute Engine, 3968/4080 MB (1020 MB allocatable), 24MCU

Benchmark relevant options:
===========================
* --opencl-device-types=2
* --optimized-kernel-enable

---------------------------------------------
* Hash-Mode 11600 (7-Zip) [Iterations: 16384]
---------------------------------------------

* Device #4: Not enough allocatable device memory for this attack.

Speed.#5.........:   166.0 kH/s (70.01ms) @ Accel:16 Loops:4096 Thr:128 Vec:1
Speed.#*.........:   166.0 kH/s

Started: Mon Apr 11 13:23:41 2022
Stopped: Mon Apr 11 13:23:44 2022





Actual hash



Quote:***@***-MacBook-Pro hashcat % ./hashcat -m 11600 -a 0 -O ../../Desktop/hash3.txt ../../Desktop/crackstation-human-only.txt -D 2

hashcat (v6.2.5-383-g6509351dc) starting



* Device #4: Apple's OpenCL drivers (GPU) are known to be unreliable.

             You have been warned.



* Device #5: Apple's OpenCL drivers (GPU) are known to be unreliable.

             You have been warned.



METAL API (Metal 261.13)

========================

* Device #1: AMD Radeon Pro 5500M, skipped

* Device #2: Intel(R) UHD Graphics 630, skipped



OpenCL API (OpenCL 1.2 (Feb 12 2022 01:56:27)) - Platform #1 [Apple]

====================================================================

* Device #3: Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz, skipped

* Device #4: Intel(R) UHD Graphics 630, 704/1536 MB (192 MB allocatable), 24MCU

* Device #5: AMD Radeon Pro 5500M Compute Engine, 3968/4080 MB (1020 MB allocatable), 24MCU



This hash-mode is known to emit multiple valid candidates for the same hash.

Use --keep-guessing to continue attack after finding the first crack.



Minimum password length supported by kernel: 0

Maximum password length supported by kernel: 20



Counting lines in ../../Desktop/hash3.txt. Please be patient..Hashes: 1 digests; 1 unique digests, 1 unique salts

Bitmaps: 16 bits, 65536 entries, 0x0000ffff mask, 262144 bytes, 5/13 rotates

Rules: 1



Optimizers applied:

* Optimized-Kernel

* Zero-Byte

* Single-Hash

* Single-Salt



Watchdog: Temperature abort trigger set to 100c



* Device #4: Not enough allocatable device memory for this attack.



Host memory required for this attack: 916 MB



Dictionary cache hit:

* Filename..: ../../Desktop/crackstation-human-only.txt

* Passwords.: 63941069

* Bytes.....: 716441107

* Keyspace..: 63941069



[s]tatus [p]ause [b]ypass [c]heckpoint [f]inish [q]uit => s



Session..........: hashcat

Status...........: Running

Hash.Mode........: 11600 (7-Zip)

Hash.Target......: $7z$0$19$0$1122$8$22a78cd81a650b0c0000000000000000$...31a6fb

Time.Started.....: Mon Apr 11 13:16:40 2022 (6 secs)

Time.Estimated...: Mon Apr 11 22:15:06 2022 (8 hours, 58 mins)

Kernel.Feature...: Optimized Kernel

Guess.Base.......: File (../../Desktop/crackstation-human-only.txt)

Guess.Queue......: 1/1 (100.00%)

Speed.#5.........:     1979 H/s (22.35ms) @ Accel:2 Loops:4096 Thr:128 Vec:1

Speed.#*.........:     1979 H/s

Recovered.Total..: 0/1 (0.00%) Digests

Progress.........: 6186/63941069 (0.01%)

Rejected.........: 42/6186 (0.68%)

Restore.Point....: 6179/63941069 (0.01%)

Restore.Sub.#5...: Salt:0 Amplifier:0-1 Iteration:520192-524288

Candidate.Engine.: Device Generator

Candidates.#5....: !@#JEYA -> !jade3

Hardware.Mon.SMC.: Fan0: 64%, Fan1: 64%

Hardware.Mon.#5..: Temp: 63c Util:  0%



Cracking performance lower than expected?                 



* Append -w 3 to the commandline.

  This can cause your screen to lag.



* Append -S to the commandline.

  This has a drastic speed impact but can be better for specific attacks.

  Typical scenarios are a small wordlist but a large ruleset.



* Update your backend API runtime / driver the right way:

  https://hashcat.net/faq/wrongdriver



* Create more work items to make use of your parallelization power:

  https://hashcat.net/faq/morework



[s]tatus [p]ause [b]ypass [c]heckpoint [f]inish [q]uit => q



Session..........: hashcat                                

Status...........: Quit

Hash.Mode........: 11600 (7-Zip)

Hash.Target......: $7z$0$19$0$1122$8$22a78cd81a650b0c0000000000000000$...31a6fb

Time.Started.....: Mon Apr 11 13:16:40 2022 (1 min, 20 secs)

Time.Estimated...: Mon Apr 11 22:21:37 2022 (9 hours, 3 mins)

Kernel.Feature...: Optimized Kernel

Guess.Base.......: File (../../Desktop/crackstation-human-only.txt)

Guess.Queue......: 1/1 (100.00%)

Speed.#5.........:     1956 H/s (20.18ms) @ Accel:2 Loops:4096 Thr:128 Vec:1

Speed.#*.........:     1956 H/s

Recovered.Total..: 0/1 (0.00%) Digests

Progress.........: 154271/63941069 (0.24%)

Rejected.........: 671/154271 (0.43%)

Restore.Point....: 154263/63941069 (0.24%)

Restore.Sub.#5...: Salt:0 Amplifier:0-1 Iteration:339968-344064

Candidate.Engine.: Device Generator

Candidates.#5....: 000123p -> 0010140136718

Hardware.Mon.SMC.: Fan0: 100%, Fan1: 99%

Hardware.Mon.#5..: Temp: 86c Util:  0%



Started: Mon Apr 11 13:16:38 2022

Stopped: Mon Apr 11 13:18:01 2022





As a side note, I didn't manage to use the Metal API. Trying -d 1 or -d 2 returns "No devices found/left".
Reply


Messages In This Thread
RE: Only getting 1% of the hashrate of the benchmark - by pdo - 04-11-2022, 03:58 PM