oclHashcat v1.36 - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Deprecated; Previous versions (https://hashcat.net/forum/forum-29.html) +--- Forum: Old oclHashcat Announcements (https://hashcat.net/forum/forum-37.html) +--- Thread: oclHashcat v1.36 (/thread-4320.html) Pages:
1
2
|
oclHashcat v1.36 - philsmd - 04-25-2015 Download is here: https://hashcat.net/oclhashcat/ This version 1.36 is a wild mix of nice updates Still, all oclHashcat versions back to 1.33 share the same driver dependencies for AMD. If you have a running oclHashcat v1.33 or newer then v1.36 will work, too, without a driver update. Most important changes:
Don't forget to visit the new FAQ pages, it's worth a read: https://hashcat.net/wiki/doku.php?id=frequently_asked_questions Full changelog v1.35 -> v1.36 Quote: RE: oclHashcat v1.36 - rchange - 04-25-2015 super!!! RE: oclHashcat v1.36 - Hash-IT - 04-25-2015 Thank you everyone involved RE: oclHashcat v1.36 - garfield - 04-25-2015 Nice work! I was just about to ask when this would be available, I was anticipating RAR support but 7z support is still great! Now, if only this .rar file would repack itself as .7z :p RE: oclHashcat v1.36 - Kgx Pnqvhm - 04-25-2015 Running the subsets of the benchmarks I use to avoid cudaHashcat crashing in Windows, I get a funny result for hash-type=10700. The tail end of c1.35 gets: >cudaHashcat64.exe --benchmark --hash-type=10600 cudaHashcat v1.35 starting in benchmark-mode... Device #1: GeForce GTX 970, 4096MB, 1240Mhz, 13MCU Hashtype: PDF 1.7 Level 3 (Acrobat 9) Workload: 1024 loops, 256 accel Speed.GPU.#1.: 1155.8 MH/s Started: Sat Apr 25 16:21:03 2015 Stopped: Sat Apr 25 16:21:19 2015 >cudaHashcat64.exe --benchmark --hash-type=10700 cudaHashcat v1.35 starting in benchmark-mode... Device #1: GeForce GTX 970, 4096MB, 1240Mhz, 13MCU Hashtype: PDF 1.7 Level 8 (Acrobat 10 - 11) Workload: 64 loops, 8 accel Speed.GPU.#1.: 14537 H/s Started: Sat Apr 25 16:21:19 2015 Stopped: Sat Apr 25 16:21:35 2015 But now in v1.36 I get: >cudaHashcat64.exe --benchmark --hash-type=10600 cudaHashcat v1.36 starting in benchmark-mode... Device #1: GeForce GTX 970, 4096MB, 1240Mhz, 13MCU Hashtype: PDF 1.7 Level 3 (Acrobat 9) Workload: 1024 loops, 256 accel Speed.GPU.#1.: 1163.8 MH/s Started: Sat Apr 25 16:18:41 2015 Stopped: Sat Apr 25 16:18:58 2015 >cudaHashcat64.exe --benchmark --hash-type=10700 cudaHashcat v1.36 starting in benchmark-mode... Device #1: GeForce GTX 970, 4096MB, 1240Mhz, 13MCU Hashtype: PDF 1.7 Level 8 (Acrobat 10 - 11) Workload: 64 loops, 8 accel Speed.GPU.#1.: 0 H/s Started: Sat Apr 25 16:18:58 2015 Stopped: Sat Apr 25 16:19:24 2015 Is there some problem with the NVIDIA kernel or some other problem? RE: oclHashcat v1.36 - epixoip - 04-26-2015 (04-25-2015, 11:28 PM)Kgx Pnqvhm Wrote: Is there some problem with the NVIDIA kernel or some other problem? Nah, default workload is just too large. RE: oclHashcat v1.36 - Rolf - 04-26-2015 Some quirks for current 7z implementation:
RE: oclHashcat v1.36 - philsmd - 04-26-2015 point 1. and 2. shouldn't be a problem in the future, because I've developed a perl script (7z2hashcat.pl) that should be able to deal with those archive types too. I.e. it does not have those limitations that 7z2john.py has... This tool is currently in testing phase (by me and atom), but I plan to release it on github soon. I also think with this new info and knowledge, we could help to improve 7z2john too... so maybe I will also provide a "patch" for 7z2john in the future... (btw further discussion about 7z2hashcat should probably have its own forum thread in the future... maybe after we release 7z2hashcat!?) RE: oclHashcat v1.36 - Kgx Pnqvhm - 04-26-2015 (04-26-2015, 06:03 AM)epixoip Wrote:(04-25-2015, 11:28 PM)Kgx Pnqvhm Wrote: Is there some problem with the NVIDIA kernel or some other problem? Running the benchmarks in previous versions worked, so is this something the hashcat devs should change? So that benchmarks should be compared to benchmarks fairly? To re-run the benchmarks for 10700 what should I use? RE: oclHashcat v1.36 - atom - 04-27-2015 -m 10700 -b --benchmark-mode 0 -u 1024 -n 1 then increase the -n value to find the sweet spot |