way to distribute cracking ?

[nextnext]

Hi All, 

I have more than one cracking rig, and I want to distribute the cracking load in these rigs. whats the best way or tool to do this ?

Thanks

[winxp5421]

https://github.com/s3inlc/hashtopussy/

Read, learn, love.

[nextnext]

https://github.com/s3inlc/hashtopussy/

Read, learn, love.

Thanks alot for sharing this.

but I saw a software called HashView , now it has a beta version (0.7) that support distributed cracking. it has many amazing feature such as (users,reporting,pausing the cracking to continue later,queuing, nice gui,..)
https://github.com/hashview/hashview/tree/0.7-beta

and the amazing Casey (one of hashView developer) has posted that he achieved 1 TH/s ! using multiple cracking systems.
https://twitter.com/CaseyCammilleri/stat...3508339712

did any one tried it ? and what do you think about it ?

[epixoip]

The hardware and underlying software are primarily responsible for speed. The wrapper's role with regards to speed is fairly minimal, in that it needs to perform efficiently to minimize the overheard associated with distributing work. The wrapper can't just magically pull 1 TH on its own, the hardware in the cluster and the backend software have to already be capable of achieving those numbers; the wrapper's job is to not fuck it up and kill performance with too much overhead. Without knowing the hardware in the cluster or the attack ran, we have no way of knowing how efficient the wrapper is. Therefore claiming it is capable of achieving some number is meaninglessness.

Also 1 TH isn't really that spectacular. We've built Hashcat clusters that achieve over 6.5 TH @ 99.2% efficiency.

[soxrok2212]

Well winxp, looks like you have a little competition  Hashview looks very nice, but I can't actually comment on the functionality or responsiveness of the UI.

epixoip, 6.5TH at 99.2% efficiency are some really crazy numbers.

[epixoip]

epixoip, 6.5TH at 99.2% efficiency are some really crazy numbers.

Hashstack - It's Hashcat on Catnip!™

[soxrok2212]

epixoip, 6.5TH at 99.2% efficiency are some really crazy numbers.

Hashstack - It's Hashcat on Catnip!™

Not to bring it off topic, but I'm also hoping to see how shitty Vega performs in hashcat benchmarks

[kjs]

The hardware and underlying software are primarily responsible for speed. The wrapper's role with regards to speed is fairly minimal, in that it needs to perform efficiently to minimize the overheard associated with distributing work. The wrapper can't just magically pull 1 TH on its own, the hardware in the cluster and the backend software have to already be capable of achieving those numbers; the wrapper's job is to not fuck it up and kill performance with too much overhead. Without knowing the hardware in the cluster or the attack ran, we have no way of knowing how efficient the wrapper is. Therefore claiming it is capable of achieving some number is meaninglessness.

Also 1 TH isn't really that spectacular. We've built Hashcat clusters that achieve over 6.5 TH @ 99.2% efficiency.

Very impressive results there.  Out of interest what hash algorithm / hash type was that result attained with?

[kjs]

epixoip, 6.5TH at 99.2% efficiency are some really crazy numbers.

Hashstack - It's Hashcat on Catnip!™

Not to bring it off topic, but I'm also hoping to see how shitty Vega performs in hashcat benchmarks

I'll have my Vega cards here in a few days and will post benchmarks ASAP thereafter.

I have AMD Vega air cooled and liquid cooled versions coming. Not exactly expecting anything great but we will see.

[epixoip]

Single hash NTLM brute force. We usually use NTLM when advertising cluster speeds since it's most relevant to pentesters & blue teams.