hashcat Forum

Every member please try to keep forum organized and post all bug related with oclhashcat-lite v0.8 here.

Any unrelated posts will be removed without warning.

Thanks

---

Skipped 1 of 8 GPU's but in status GPU's are aligned incorectly, displayed not by the order, skipped GPU not shown anymore either.

In this example I have here 8 GPU rig , and #7 GPU failed, I skip this specific GPU with command line: -d 1,2,3,4,5,6,8

program launches, shows skipped gpu in first run, and in status display prompt it shows #7 gpu active and #8 gpu missing etc

https://paste2.org/p/1853330

Thanks

Hello, 1º sorry for my bad english.
2º i have a problem with the new 0.8 version with SL3, thit 2 phones have the 100% and no cod file.
i tray with the old 0.6 (with this never have problems) and the 2 phones have de cod file OK.

¿how i can help you to fix this?

Thanks

oclhashcat-lite v0.8 not working "Assume salt is given in hex"

what is the exact problem?

(01-30-2012, 05:21 PM)atom Wrote: [ -> ]what is the exact problem?

example:
oclHashcat-lite64.exe --hash-type 15 4a80a448a4a5c5d20024cba8a3c779dd:?$x&XL5w>\c*7,F03G=v~0`THUP{,b

oclHashcat-lite v0.8 by atom starting...

ERROR: hash: 4a80a448a4a5c5d20024cba8a3c779dd:?$x, line length exception: 36
ERROR: invalid hash '4a80a448a4a5c5d20024cba8a3c779dd:?$x'. double check -m para
meter
_________________________________________________________
the same in hex:

oclHashcat-lite64.exe --hex-salt --hash-type 15 4a80a448a4a5c5d20024cba8a3c779dd:3F247826584C35773E5C632A372C463033473D767E3060544855507B2C62

ERROR: hash: 4a80a448a4a5c5d20024cba8a3c779dd:3F247826584C35773E5C632A372C463033
473D767E3060544855507B2C62, line length exception: 93
ERROR: invalid hash '4a80a448a4a5c5d20024cba8a3c779dd:3F247826584C35773E5C632A37
2C463033473D767E3060544855507B2C62'. double check -m parameter
----------------------------------------------------------------------
Maybe I do not understand that? a reaction to the character "&"
but in oclHashcat-plus it works

oclHashcat-plus64.exe --hash-type 2711 --attack-mode 3 --custom-charset1 ?l?d --hex-charset --hex-salt 4a80a448a4a5c5d20024cba8a3c779dd:3F247826584C35773E5C632A372C463033473D767

Status.......: Running
Input.Mode...: Mask (?1?1?1?1?1?1?1)
Hash.Target..: 4a80a448a4a5c5d20024cba8a3c779dd:3f247826584c35773e5c632a372c4630
33473d767e3060544855507b2c62
Hash.Type....: vBulletin > v3.8.5
Time.Running.: 49 secs
Time.Left....: 22 secs
Time.Util....: 49741.8ms/292.8ms Real/CPU, 0.6% idle
Speed........: 1090.9M c/s Real, 1565.1M c/s GPU
Recovered....: 0/1 Digests, 0/1 Salts
Progress.....: 54263808000/78364164096 (69.25%)
Rejected.....: 0/54263808000 (0.00%)
HW.Monitor.#1: 73% GPU, 85c Temp
HW.Monitor.#2: 73% GPU, 85c Temp
[s]tatus [p]ause [r]esume [q]uit =>

looks like you copied some strange html content in your report. i had to convert it to hex again and then it worked fine. here is my log:

Quote:root@sf:~/oclHashcat-lite-0.09# ./oclHashcat-lite64.bin --hex-salt --hash-type 2711 4a80a448a4a5c5d20024cba8a3c779dd:3f247826584c35773e5c632a372c463033473d767e3060544855507b2c62
oclHashcat-lite v0.9 by atom starting...

** Valid keyfile for beta usage: atom (expires 29.01.2013)

GPU-Loops: 64
GPU-Accel: 160
Password lengths range: 4 - 55
Platform: AMD compatible platform found
Watchdog: Temperature limit set to 90c
Device #1: Cypress, 512MB, 0Mhz, 20MCU
Device #2: Cypress, 512MB, 0Mhz, 20MCU
[s]tatus [p]ause [r]esume [q]uit => s
Status.......: Running
Hash.Target..: 4a80a448a4a5c5d20024cba8a3c779dd:3f247826584c35773e5c632a372c463033473d767e3060544855507b2c62
Hash.Type....: vBulletin > v3.8.5
Time.Running.: 3 secs
Time.Left....: 1 min, 2 secs
Plain.Mask...: ?1?2?2?2?2?2?2
Plain.Text...: ***aaaa
Plain.Length.: 7
Progress.....: 7471104000/134960504832 (5.54%)
Speed.GPU.#1.: 1011.9M/s
Speed.GPU.#2.: 1011.9M/s
Speed.GPU.#*.: 2023.7M/s
HWMon.GPU.#1.: 91% GPU, 48c Temp
HWMon.GPU.#2.: 92% GPU, 44c Temp

(01-30-2012, 06:48 PM)atom Wrote: [ -> ]looks like you copied some strange html content in your report. i had to convert it to hex again and then it worked fine. here is my log:

Quote:root@sf:~/oclHashcat-lite-0.09# ./oclHashcat-lite64.bin --hex-salt --hash-type 2711 4a80a448a4a5c5d20024cba8a3c779dd:3f247826584c35773e5c632a372c463033473d767e3060544855507b2c62
oclHashcat-lite v0.9 by atom starting...

** Valid keyfile for beta usage: atom (expires 29.01.2013)

GPU-Loops: 64
GPU-Accel: 160
Password lengths range: 4 - 55
Platform: AMD compatible platform found
Watchdog: Temperature limit set to 90c
Device #1: Cypress, 512MB, 0Mhz, 20MCU
Device #2: Cypress, 512MB, 0Mhz, 20MCU
[s]tatus [p]ause [r]esume [q]uit => s
Status.......: Running
Hash.Target..: 4a80a448a4a5c5d20024cba8a3c779dd:3f247826584c35773e5c632a372c463033473d767e3060544855507b2c62
Hash.Type....: vBulletin > v3.8.5
Time.Running.: 3 secs
Time.Left....: 1 min, 2 secs
Plain.Mask...: ?1?2?2?2?2?2?2
Plain.Text...: ***aaaa
Plain.Length.: 7
Progress.....: 7471104000/134960504832 (5.54%)
Speed.GPU.#1.: 1011.9M/s
Speed.GPU.#2.: 1011.9M/s
Speed.GPU.#*.: 2023.7M/s
HWMon.GPU.#1.: 91% GPU, 48c Temp
HWMon.GPU.#2.: 92% GPU, 44c Temp

look at my example above, I added it
I have win 7 and you have a Linux
We have different versions of programs, work with me 0.8 and you have 0.9
hash type is also different! 0.8 version does not support hash-type 2711 only -m 15
we are comparing two different things ...
how to become a beta tester of the new 0.09 version?
Thank you very much for your work!

@lindros, atom is the creator of the tool, that's why atom has a beta version.

oclHashcat-plus 0.07 changed the identifying number for vBulletin hash types. It's a cosmetic change. The beta of oclHashcat-lite is changing to match the identifiers used by oclHashcat-plus 0.07. Nothing to see here...

I guess for vBulletin it's easier to convert the salt to hex, since it's very common for the salt to contain characters that are shell reserved characters.

(01-30-2012, 08:56 PM)chort Wrote: [ -> ]@lindros, atom is the creator of the tool, that's why atom has a beta version.

oclHashcat-plus 0.07 changed the identifying number for vBulletin hash types. It's a cosmetic change. The beta of oclHashcat-lite is changing to match the identifiers used by oclHashcat-plus 0.07. Nothing to see here...

I guess for vBulletin it's easier to convert the salt to hex, since it's very common for the salt to contain characters that are shell reserved characters.

I think you're casually reading my post ...
I always translate to hex my salt
but I have Win 7 and hex salt only works in the program oclHashcat-plus
but this program is slower than oclhashcat-lite
I wanted to worked oclhashcat-lite with hex salt
I think , Atom will understand what was going on
thanks

I was pasting this over ssh and it seems like something got interpreted as control characters, because my terminal got messed up (cursor at the wrong location, typed characters appeared incorrect).


However simply quoting the hash and salt works:

I did get an error after quitting and restarting that oclHashcat-lite could not read the restore file. I simply rm'd the restore file and I was able to start another session just fine.