Posts: 5,185
Threads: 230
Joined: Apr 2010
you may need to cut away the hashes. use cut (port also exists for windows) from unix utils package.
cut -b34- < foundpasswords.txt > foundpasswords.txt.cut
Posts: 621
Threads: 57
Joined: May 2010
This will be a problem with MD5(unix) hashes that don`t always have the same length...
Posts: 5,185
Threads: 230
Joined: Apr 2010
true. i will add it to oclhashcat+ in a later version.
Posts: 134
Threads: 27
Joined: May 2010
02-12-2011, 03:55 PM
(This post was last modified: 02-12-2011, 04:21 PM by proinside.)
I've edited the title thread but fail to post my comment.
Sor, here it is:
While running a large md5 file (above 1,5 m hashes), we get a number
of lines with the message "...line lenght exception error...", and this
happens every time we start a new rule/new attack.
The doubt is: if oclhashcat+ detects those line errors, would be
logical to delete those lines, so the errors don't repeat each time
we start all over again ?
Can those lines be deleted, once detected at the start, and, eventually
copy the line which cause the error message to a new file for a check
of what is causing the error message ?
Take it as a constructive suggestion, of course.
Thanks.
Posts: 5,185
Threads: 230
Joined: Apr 2010
thats something it will do if it has --remove switch. till then, use hashcat cpu version to do it / see how it behaves
Posts: 5,185
Threads: 230
Joined: Apr 2010
has been added in the meanwhile. thread closed.