oclHashcat v1.20

[richk]

Well in case anyone is interested here's a link to instructions for upgrading libc on The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali). Note that you're installing from the debian sid (unstable) repository so it could break stuff. As of right now, cudaHashcat-1.20 is working great on The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) after the upgrade. Did the upgrade break other programs on The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali)? I don't know. Time will tell.

Link:
https://forums.The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali).org/showthread.php?18899-Glibc-2-14-upgrade-for-using-yara-python

Actual Instructions from the site:

I was able to install libc6 2.17

IMPORTANT*
You need to exit out of your display manager by pressing CTRL-ALT-F1.
Enter root credentials.
Then you can stop x with /etc/init.d/slim stop

(replace slim with mdm or lightdm or gdm3 or whatever your current display manager is)

Add the following line to the file /etc/apt/sources.list: (nano /etc/apt/sources.list)

deb http://ftp.debian.org/debian sid main

Update your package database:
apt-get update

Install the eglibc package:

apt-get -t sid install libc6-amd64 libc6-dev

IMPORTANT
After done updating libc6, restart computer, and you should comment out or remove the sid source you just added (deb http://ftp.debian.org/debian sid main), or else you risk upgrading your whole distro to sid and will most likely corrupt your distro.

Hope this helps. It took me a while to figure out.

On a scale of 1-10 i would give this a -1,234,765 score on what to do. Upgrading your libc library to the unstable sid version WILL break many of The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali)'s features [Trust me, I have already tried this... and test every method of fixing it.. There is none]. Should ask atom to do what bitcoin did and make a static link to the old libraries... Otherwise, don't have 1.20 installed on The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) and wait... or wait for a fix from The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) members [that doesn't involve using an unstable version of libc... I assure you, it will break...]

I agree, and I mentioned as such in my message. Messing with libc is generally bad, but if you know what you're doing, and none of the other programs you are using on The-Distribution-Which-Does-Not-Handle-OpenCL-Well (Kali) are broken by upgrading then go for it. If you're cracking passwords I assume you have enough knowledge to understand the implications of doing something like this.

Atom, what are the chances of getting a version with a static link to the old libraries until Debian upgrades libc in the next version?