(04-06-2015, 04:38 PM)epixoip Wrote:(04-05-2015, 10:13 PM)InfDoleo Wrote: odd restriction
programming limitation
To top it off - closed source - I can't just change the code
If you don't understand the restriction nor why it exists, what makes you think you'd be any better off having the source code?
So that I CAN understand why it exists, and modify it if necessary.
If a combination or mask attack CAN be longer than 31, it's not that its completely impossible. If it has to do with 32 bytes of space in the GPU itself, and it's fed the data differently because of the way combination and mask attacks work, there doesnt seem to be any good reason why a straight dictionary attack wouldnt either. Split the string in 2 parts before feeding it in, and simulate a combination attack.
If it's not that simple because the combining is done IN the GPU, then you find a workaround. And if thats not possible, then you LEARN why. Learning why is always preferable to "No. Just because."
And, since it's closed source, it therefore IS impossible, instead of maybe possible.
That being said there was a reply in my other thread that seems to show a way to do it using rule-based attacks, something I hadn't yet read up on.
Doesn't change the fact that it sucks it's closed source. There are other things I'd like to do with GPU hashing that it seems like oclhashcat does MUCH better than the open source solutions like cgminer and the like. I have an app I want to research, and having a solid starting point in a programming area I am not familiar with, GPU interfacing, would have been nice.
Not sure why the heck I'm being jumped upon here.