Ok so for giggles I did some testing, and accidentally came across something.
Here's the benchmark for MD5
Here's an attack for MD5, done wrong.
hashcat64.exe --stdout d:\wordlists\rockyou.txt -r rules\best64.rule | hashcat64.exe -m0 -a3 d:\hashlists\Random\Quillen.txt -O --status --status-timer=2
That -a3 shouldn't be there (typo on my part) but look at the output
And look at the Guess.Charset, which is what you would expect from a basic brute force. It's not using the parameters (rule/wordlist) from the first instance of hashcat that's being piped to the second one. Yet, when I correct that -a3 by removing it OR putting an -a0 in there, I get this -
It's acting like a basic dictionary lookup and ignores the rules parameter completely.
Now I'm really confused. I was going to relocate one of the cards to the MB to test, but this tells me the hardware is just fine. Something else is keeping that hardware from being utilized unless something funky happens with the command. Ideas?
Edit - both this rig and my desktop have the same drivers and are updated Windows 10
Here's the benchmark for MD5
Quote: Hashmode: 0 - MD5
Speed.#1.........: 41444.7 MH/s (18.21ms) @ Accel:64 Loops:1024 Thr:256 Vec:4
Speed.#2.........: 33367.6 MH/s (27.55ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Speed.#3.........: 19730.0 MH/s (50.48ms) @ Accel:256 Loops:1024 Thr:256 Vec:4
Speed.#4.........: 18815.4 MH/s (38.72ms) @ Accel:128 Loops:1024 Thr:256 Vec:4
Speed.#*.........: 113.4 GH/s
Here's an attack for MD5, done wrong.
hashcat64.exe --stdout d:\wordlists\rockyou.txt -r rules\best64.rule | hashcat64.exe -m0 -a3 d:\hashlists\Random\Quillen.txt -O --status --status-timer=2
That -a3 shouldn't be there (typo on my part) but look at the output
Quote: Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: (redacted)
Time.Started.....: Sat Aug 31 11:53:43 2019 (19 secs)
Time.Estimated...: Sat Aug 31 11:54:34 2019 (32 secs)
Guess.Mask.......: ?1?2?2?2?2?2?2?3 [8]
Guess.Charset....: -1 ?l?d?u, -2 ?l?d, -3 ?l?d*!$@_, -4 Undefined
Guess.Queue......: 8/15 (53.33%)
Speed.#1.........: 39630.7 MH/s (9.13ms) @ Accel:64 Loops:512 Thr:256 Vec:4
Speed.#2.........: 31296.3 MH/s (6.96ms) @ Accel:128 Loops:256 Thr:256 Vec:4
Speed.#3.........: 18150.8 MH/s (6.39ms) @ Accel:256 Loops:128 Thr:256 Vec:4
Speed.#4.........: 17768.5 MH/s (9.85ms) @ Accel:128 Loops:256 Thr:256 Vec:4
Speed.#*.........: 106.8 GH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 2072621613056/5533380698112 (37.46%)
Rejected.........: 0/2072621613056 (0.00%)
Restore.Point....: 18841600/68864256 (27.36%)
Restore.Sub.#1...: Salt:0 Amplifier:55808-56320 Iteration:0-512
Restore.Sub.#2...: Salt:0 Amplifier:18688-18944 Iteration:0-256
Restore.Sub.#3...: Salt:0 Amplifier:36736-36864 Iteration:0-128
Restore.Sub.#4...: Salt:0 Amplifier:76288-76544 Iteration:0-256
Candidates.#1....: lo18164a -> 94kzrr6t
Candidates.#2....: 5mswrr6t -> zclnjo1c
Candidates.#3....: M5btwh6c -> Bjl6804a
Candidates.#4....: 81yw8w0a -> Bbx68s5c
Hardware.Mon.#1..: Temp: 51c Fan: 38% Util: 96% Core:2010MHz Mem:6800MHz Bus:1
Hardware.Mon.#2..: Temp: 45c Fan: 22% Util: 96% Core:1822MHz Mem:5005MHz Bus:1
Hardware.Mon.#3..: Temp: 58c Fan: 8% Util: 95% Core:1999MHz Mem:3802MHz Bus:1
Hardware.Mon.#4..: Temp: 67c Fan: 0% Util: 96% Core:1366MHz Mem:3304MHz Bus:1
And look at the Guess.Charset, which is what you would expect from a basic brute force. It's not using the parameters (rule/wordlist) from the first instance of hashcat that's being piped to the second one. Yet, when I correct that -a3 by removing it OR putting an -a0 in there, I get this -
Quote:Session..........: hashcat
Status...........: Running
Hash.Type........: MD5
Hash.Target......: (redacted)
Time.Started.....: Sat Aug 31 12:15:01 2019 (19 secs)
Time.Estimated...: Sat Aug 31 12:15:20 2019 (0 secs)
Guess.Base.......: Pipe
Speed.#1.........: 148.8 kH/s (0.17ms) @ Accel:64 Loops:1 Thr:256 Vec:1
Speed.#2.........: 181.1 kH/s (0.41ms) @ Accel:128 Loops:1 Thr:256 Vec:1
Speed.#3.........: 257.5 kH/s (0.44ms) @ Accel:256 Loops:1 Thr:256 Vec:1
Speed.#4.........: 189.1 kH/s (0.29ms) @ Accel:128 Loops:1 Thr:256 Vec:1
Speed.#*.........: 776.6 kH/s
Recovered........: 0/1 (0.00%) Digests, 0/1 (0.00%) Salts
Progress.........: 8421448
Rejected.........: 72
Restore.Point....: 0
Restore.Sub.#1...: Salt:0 Amplifier:0-1 Iteration:0-1
Restore.Sub.#2...: Salt:0 Amplifier:0-1 Iteration:0-1
Restore.Sub.#3...: Salt:0 Amplifier:0-1 Iteration:0-1
Restore.Sub.#4...: Salt:0 Amplifier:0-1 Iteration:0-1
Candidates.#1....: snopsnop -> /avid
Candidates.#2....: d00davi -> tweetyie
Candidates.#3....: moza -> oliv3r21
Candidates.#4....: olver21 -> snoo88
Hardware.Mon.#1..: Temp: 31c Fan: 36% Util: 0% Core:1515MHz Mem:7500MHz Bus:1
Hardware.Mon.#2..: Temp: 27c Fan: 40% Util: 0% Core:1480MHz Mem:5103MHz Bus:1
Hardware.Mon.#3..: Temp: 29c Fan: 40% Util: 0% Core:1632MHz Mem:3802MHz Bus:1
Hardware.Mon.#4..: Temp: 32c Fan: 52% Util: 0% Core:1189MHz Mem:3304MHz Bus:1
It's acting like a basic dictionary lookup and ignores the rules parameter completely.
Now I'm really confused. I was going to relocate one of the cards to the MB to test, but this tells me the hardware is just fine. Something else is keeping that hardware from being utilized unless something funky happens with the command. Ideas?
Edit - both this rig and my desktop have the same drivers and are updated Windows 10