03-31-2013, 09:51 PM
(03-31-2013, 12:34 PM)atom Wrote: 2nd one might be because oclhashcat works a lot different internal with its memory handling in rules than hashcat. for example oclhashcat-plus does have only a 16 byte temporary buffer and does not skip once a not matching rule is applied. for example, if the input word has the length 9 and you use the double rule it gets length 18 last 2 byte not are missing in oclhashcat. in hashcat that would not happend. now if another rule is aplied that would remove lets say the first 4 characters, then the length becomes length 15 so its "ok", however, in oclhashcat the 2 byte got missing ffrom the first so the length in oclhashcat-plus will be length 11
That makes sense and I think I understand that
hey there has to be a first time 
I am trying to word this next bit very carefully, as I don't want to sound ungrateful or critical.
I am noticing more and more problems, both with things I would like to do personally and things others are experiencing independently which seem to be coming down to the password length restrictions in oclhashcat.
Like I say, I am massively grateful for oclhashcat and I do not pretend to understand the difficulties in writing such software. Just speaking purely as a humble user the "password length issue" is starting to become a real problem for me and others.
I understand you are considering the options regarding this and also working out the difficulties. Can you please give us a news update and perhaps let us know your thoughts as to where you are taking oclhashcat ?
Thank you.