![]() |
OclHashcat+ --remove option / line lenght exception error - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Deprecated; Ancient Versions (https://hashcat.net/forum/forum-46.html) +--- Forum: Very old oclHashcat-plus Support (https://hashcat.net/forum/forum-23.html) +--- Thread: OclHashcat+ --remove option / line lenght exception error (/thread-270.html) Pages:
1
2
|
RE: OclHashcat+ --remove option / line lenght exception error - atom - 02-05-2011 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 RE: OclHashcat+ --remove option / line lenght exception error - mastercracker - 02-09-2011 This will be a problem with MD5(unix) hashes that don`t always have the same length... RE: OclHashcat+ --remove option / line lenght exception error - atom - 02-09-2011 true. i will add it to oclhashcat+ in a later version. RE: OclHashcat+ --remove option / line lenght exception error - proinside - 02-12-2011 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. RE: OclHashcat+ --remove option / line lenght exception error - atom - 02-13-2011 thats something it will do if it has --remove switch. till then, use hashcat cpu version to do it / see how it behaves RE: OclHashcat+ --remove option / line lenght exception error - atom - 10-24-2011 has been added in the meanwhile. thread closed. |