mxkey sl3bf attack problem [solved]

[amitgoody]

so before telling the problem let get know how the sl3bf of mxkey works




here you can see the that
sl3bf->IMEI: 35430504977982
sl3bf->HASH: E33901758823D58EEAA67BEDCDF850EAFBCCB60D
sl3bf->SALT: 03000800
sl3bf->start child targeting 11 digit password.
sl3bf->CMDLINE: --gpu-watchdog=0 -m 110 -n 160 --pw-min=11 --pw-max=11 --hex-charset --hex-salt --outfile-format=4 --outfile=__out.txt -1 00010203040506070809 E33901758823D58EEAA67BEDCDF850EAFBCCB60D:030008000 03543050497798200 ?1?1?1?1?1?1?1?1?1?1?1
sl3bf->end child (elapsed 36614 ms)


that 3080 is the salt of which we cannot get any % status represented by
GUI as the process of oclhastcat-lite.exe is not been opened successfully by sl3bf.exe
this could lead to the following:

that if the master code with salt 3080 will not be recognized by the sl3bf.exe and hence may be your right code will be lost and even after your run this 100 % you wont get a code...


2 nd case this is running fine as we can get the status successfully
and if the code is hit than i will be known to the sl3bf.exe and hence it will show "success".

so now how to get it
so go to the location
C:\mobileEx\3.5\modules\{3EBAF427-9F55-419F-8A75-385DFC651169}

and you will find the .log files like sl3bf.log

now open it and ctrl+f then find elapsed 1

this will all the process that will have been terminated in 10 sec as my 100% for one salt time is 35.5-36.5 sec
hence if salt hits then it would be in 1-29 sec
so when we search for elapsed 1 or elapsed 2

you can see here

so the solution is
regularly check for log file by this
search "elapsed (10-80 % time ) of the your one salt time "
[COLOR=*****Brown]like in my photos my normal salt time is about 3652ms

so if hit is there then the process would have been terminated in 1000-2900 ms

so i search for "elapsed 1 " or "elapsed 2".


so let request Mr. manole to make a fix.....
[/COLOR]