hashcat Forum

Welcome to oclHashcat-lite v0.10.

Download it here: https://hashcat.net/oclhashcat-lite/

This release is a big step forward. We have added both, many major and many minor features.

Per-position markov-chains, aka markov-attack/incremental-attack/charset-files

The markov-attack is a statistically based brute-force like attack, but instead of specifying a charset or a mask, we specify a file. This file is once generated by ourself in a previous step. It contains statistical informations which are made out an automated analysis of a given dictionary.

It can fully replace Brute-Force since it covers the full keyspace.

In Brute-Force Attack (or in Mask Attack) we can limit the keyspace by setting a smaller charset in order to reduce the attack-time. In Markov Attack we have something similar, the "threshold". All you do is to specify a number. The higher the number, the higher the threshold to add a new link between two characters on the two-level table on which the markov-attack bases on.

This background is not so important, just remember that the lower the value, the smaller the keyspace and thus the faster the attack is.

Check these threads for more details

• https://hashcat.net/forum/thread-1265.html
  
• https://hashcat.net/forum/thread-1285.html
  
• https://hashcat.net/forum/thread-1291.html
  

Use .ptx ad .llvmir intermediate kernels

The kernels are distributed in an "intermediate" format (aka IL). It cant be reversed to original C code but still its not a binary format that can be used for execution.

The JIT (just-in-time) compilers from both OpenCL and CUDA, which ship with the driver, compile the final byte-code out of the IL. This takes a few seconds per kernel but once its done the byte-code is cached (CUDA does it automatically, OpenCL not but we add a function to do the same as CUDA does).

This has some nice advantages:

• Not 32/64 bit specific
  
• Less HDD space
  
• Smaller .7z
  
• Less problems with driver specific problems as we often see with Catalyst
  
• There is no more need to release a new oclHashcat-* in case a new driver optimization has been added. oclHashcat-* caches driver specific. If it recognizes a driver change it will rebuild thge byte-code from the IL, but using the new JIT from the new driver resulting in driver specific optimized byte-code.
  

Retaining GPU temperature

When I started with oclHashcat-* Hardware mangement support, some people asked me for add support for fan-speed. For a long time I was not interessted in adding fan-speed code to oclHashcat-* since this is the job for the driver or some specialized controling software.

I did not change my mind completly on this, but still we have added some fan-speed controlling code. The new parameters are:


So what this thing is doing is: If the temperature configured with the new --gpu-temp-retain parameter is reached, it starts to increase the fan-speed by 1 percent each second. Thats all.

If you imagine a scenario what this means you will come to the conclusion that this feature also enables you to enfore your GPU running always to a very specific temperature.

Some notes:

• --gpu-temp-disable you can completly disable all the temperature stuff.
  
• --gpu-temp-retain currently only works for AMD.
  
• --gpu-temp-abort parameter is just the renamed version of the old --gpu-watchdog.
  
• Both parameters accept the 0 value which disables only this specific feature. This means you can step back to the old behavior by specifying --gpu-temp-retain 0.
  
• The default for --gpu-temp-abort is still 90c.
  
• The default for --gpu-temp-retain is 80c.
  

Built-in benchmarking mode


Nothing much to explain here I think, but some notes to the benchmark mode:

• As long as you do not set the --benchmark-mode you can modify all the configuration parameters you always use. Something like -d, -n, --gpu-accel or --runtime.
  
• With --runtime you can specify the duration how long each test lasts.
  
• If you add -m you can limit to a specific hash-type. If you do not set it, it will iterate through all hash-types.
  
• All unneccessary parallel threads like hardware monitor, restore-support and outfile-watch are disabled. Also the quiet mode is enabled.
  
• On NVidia, the hashes based on SHA256, SHA512 and DES are limited to -n 32, otherwise the driver throws the error cuStreamSynchronize() 702.
  

New Algorithms supported

• SHA512
  
• Oracle 7-10g, DES(Oracle)
  
• md4($pass.$salt)
  
• sha256($pass.$salt)
  
• sha512($pass.$salt)
  

Full changelog

Great job atom! As always.
Thank you!

Cool.

Hello:
Nice Work Boss;we will give report tomorow after Test.
regrads,
multimediabox

hello; i can use dictianary attack for decrypter hash sl3
thx.

yes, use rockyou dictionary, it should help much for SL3 bruteforce, maybe 15 min/phone.

how to make rokyou dictionary and use it ?

It is not that hard to replicate KT819GM's prescription here.

First, we need to put together in our cup a "Search" button (which is on the very top) and keywords what we're interested. Then look through the results with a cat's curiosity. And finally swallow it with an atomic speed. That's it.

PS: whole process should be proceeded with a lite sense of humor, otherwise frustration is inevitable.

hi ho can explain to me step by step how to use dictinary in oclhashcat lite for sl3
it s to difficulte for me to do it by my self
thank s

(08-17-2012, 03:20 AM)korsa741 Wrote: [ -> ]hello; i can use dictianary attack for decrypter hash sl3
thx.

Oh man, there is no dictionary for lite, and will never be, it's totally random 15 digit code!

Again for SL3 people:
tag for search: sl3 dict, sl3, sl3 dictionary, dictianary, SL3 bruteforce

answer:
THERE IS NO DICTIONARY FOR SL3