Pyrit and CUDA, How To?

Hello again for another quick guide, this time I am trying to light your path to Pyrit-CUDA on Kali Linux and an hybrid notebook. By hybrid I mean, 2 GPU; 1 Intel 1 NVidia.

It was originally my first experience with gp-gpu experience and it was ridiculously hard. I mean I really gave more time and effort than actually learn to crack some WPA in the first place. Whole drivers and SDKs, finding the right libraries, correct combinations, etc... was very tiresome; I tried and crashed Kali and re-install like so many times actually forgot the count.

Anyways the below is the way I got it working with my Fujitsu Lifebook LH532, essentially it is a Core i3 notebook with a GT 620m GPU.

First thing is first, like on many Debian start with;

apt-get update

Of course if anything goes wrong you know what to do. Get a better sources.list and kernel-headers.

Then this is the critical part. It will quite possibly crash your setting if it is not like mine. But what the cow, you prolly did crashed your system so many times already; at this point you are willing to try anything...

apt-get install nvidia-detect nvidia-libopencl1 nvidia-opencl-common nvidia-support nvidia-opencl-icd nvidia-visual-profiler nvidia-glx nvidia-installer-cleanup nvidia-kernel-common nvidia-smi nvidia-alternative nvidia-opencl-dev libglx-nvidia-alternatives nvidia-kernel-dkms nvidia-cuda-toolkit nvidia-vdpau-driver nvidia-xconfig glx-alternative-nvidia libgl1-nvidia-alternatives nvidia-settings libgl1-nvidia-glx xserver-xorg-video-nvidia libcublas4 libcudart4 libcufft4 libnpp4 libnvidia-compiler libcuda1 libcuinj4 libnvidia-ml1 libxvmcnvidia1 libcusparse4 libcurand4 python-pycuda-doc python-pycuda-headers python-pycuda nvidia-cuda-doc nvidia-cuda-gdb

I found above command as a whole on a japanese blog, and cannot find again to give credit. But thanks to dude who did in the first place. I remember he stated this line should work for Ubuntu on a hybrid notebook also.

Again sources.list is very important if you intend to complete above command successfully.

If everything is still working order, then do the magic below;

/root/.bashrc <<

PATH=$PATH:/usr/lib/nvidia-cuda-toolkit/bin
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/nvidia-cuda-toolkit/lib:/lib
export PATH
export LD_LIBRARY_PATH

After this we actually have CUDA on Kali, just restart the system and see if it is still booting up :) if not well re-install Kali, sorry.

----------------------------------------------------

Now time for actually settin up Pyrit-CUDA, don't worry tho; worse is behind and there is no danger crashing after this point.

We should download the official packages from the official site. which are pyrit-0.4.0.tar.gz and cpyrit-cuda-0.4.0.tar.gz that you need. Before you do anything just get below 2 library first.

atp-get install libpcap-dev python2.7-dev

Then for Pyrit do the following;

tar -xzvf pyrit-0.4.0.tar.gz
cd pyrit-0.4.0
python setup.py build
python setup.py install

Now you have Pyrit if everything went smoothly, but not yet Pyrit-CUDA. Here goes the magic again;

tar -xzvf cpyrit-cuda-0.4.0.tar.gz
cd cpyrit-cuda-0.4.0

setup.py <<

for path in ('/usr/local/cuda', '/opt/cuda'):
>> (must be like below or appropriate)
for path in ('/usr/local/cuda','/usr/lib/nvidia-cuda-toolkit','/opt/cuda'):

python setup.py build
python setup.py install

Tadaa (Windows 3.1 sound) !!! We have Pyrit with CUDA support. Enjoy the show;

note: you can see the device by "pyrit list_cores" and test via "pyrit benchmark".

HD 7770 (x2) X-Fire Setting For OpenCL + Pyrit

Not long ago, I bought 2 HD7770 for my rig. And then decided to give a try to the Pyrit. Everyone knows Pyrit right? Ok.

It's actually pretty easy to set Pyrit up for gpu. IN THEORY! I spent 4-5 hours for my setting to operate correctly this time around... Last time I was trying Pyrit-CUDA on a hybrid gpu notebook and it was a real pain. Like real pain.

Anyhow, I use Kali as my distro cause at least it is pre-patched for all my wifi dongles. I, at least, don't bother with the firmware patching and stuff.

So let's start with the AMD-ATI official drivers. Use this script to install them, the guy who wrote is brilliant and did a tremendous amount of work. So we don't have to get through that hell every time we need to install AMD-ATI drivers. Script simply works just run it and pour a cup of coffee and enjoy.

Then we need to install AMDAPP 2.7 because the script installs drivers version 8.96 something. these can be found on official AMD site. If you somehow manage the install the drivers without above script, you probably have another version. You should check the appropriate compatible version of APP SDK and then download that specific version accordingly. You can trust the instructions on the official page. They work, unlike the driver installation part of the official AMD site.

If all is well so far, then we need some more libraries that is not included with the standard setup of KALI Linux. Below the command to do that;
apt-get install opencl-icd-dev
apt-get install libpcap0.8-dev

You may need to update kernel headers and apt-get update. I assume you are familiar with those or already done it.

Now it is time for us to compile Pyrit. We should edit cpyrit/setup.py script accordingly to this blog. Read carefully and do exactly, we should be fine. Then we compile opencl-pyrit module. We should get no error if everything is good so far.

We should be done at this point just test it if Pyrit sees your AMD OpenCL supported device by 'listcores' parameter. We should see the whole device as one single core just like a CPU core. That's OK though. Pyrit will utilize all the cores available on that OpenCL device.

Congrats, you have now acquired more power to crack WPA passwords faster. If you still have problems or could not complete the guide above for some reason, please let me know so I may be able to help.

PS: Sorry I published this post before I finished it and never realized. This is the finished version.

Installing Windows After Linux!

Hello, this time I am gonna try a different type of post. I am not gonna give any in-depth-details about the commands and stuff but rather share my experience to dual boot as installing Linux first and Windows after. First of all let me give you the configuration I have so you could judge it if you should try below steps in such operation if it suits you anyhow...

I had a single hard disk in my laptop as single partitioned (ext4) 500GB for Kali with latest updates, everything is working right, no problem in anyway. It is a very healthy system, but I will never ever never trust my NTFS formatted archive external disks with any version of Linux or Mac or anyother OS if that matters. I will never use those disk under any circumstances on other operating systems except Microsoft ones as their content is invaluable, years of backups, works, codes, datas, you know my digital life. I lost my other machine to a hardware failure and so I also wanted to have a Windows 8.1 preview version as my second OS on this machine. I downloaded from the official Microsoft site and the risky operation series has begun. I strongly suggest you to take backups before try anything. In fact don't try this at all, these are only my experiences I decided to share.

I will try to write the steps I followed in bullets, give commands or links if necessary along the way;

• Downloaded the Windows 8.1 preview iso from the official site. Just do a Bing search for it you'll quickly find it. Or click "w", I am annoying =P
• Made the iso a bootable flash drive. There are innumerable guides out there, just Bing it, or Google it.
• After that I booted my system with Kali live usb stick, and used gparted to shrink my single partition's size by 190GB, that is how much space I wanted for my Windows 8.1 Preview. Decide and shrink your partition with your live Linux USB, I believe any modern live stick will do job. {I somehow couldn't manage without this second live Linux usb stick there are guides to shrink a partition but I couldn't do it.}
• Then I booted into Windows install stick (I think you can use any version but for the sake of my experience I will assume you are using also 8.1 preview) and installed my 8.1 preview to that newly emptied free unallocated space. after installation it looked like this =>here sda1 is my Kali, sda2 (the small area between sda1 and sda3) Windows boot partition, sda3 is Win8.1Pre, last part is linux swap.
• But at this point I was cut off of from my Linux. No way to boot into. Stuck with Windows, I followed this guide I found. I know it is in Italian, I don't know any Italian. You could simply follow the commands or have Bing translate the page for you.
• And now I am stuck with only Kali, but now I had Windows installed over my disk somewhere. I just cannot boot into it. That's I figured pretty good, and thought can be a very manageable situation. But once again for the sake of the completeness of my whole experience I am gonna write the misssteps I took. In italic don't do them, just read them and go to the next bullet.
1. I booted into my Windows Install USB stick and try to recover MBR there. I succeeded with some commands from the prompt like bootsect and stuff, but that got me stuck with only Windows once again.
2. Then I re-recovered my grub from the guide above I linked, then again I was stuck with only Kali, with Windows over there unreachable.
3. I tried old distros' with the option "boot the first partition" live CDs. Nothing worked, for a time I had a very healthy Kali and an unreachable Windows.
4. Then I try some other guides I found, involving bunch of grub config file editing and grub-updates etc... those only worsen the situation. I decided the safest way to achieve my goal is to have Kali and making the whatever it is going to take manually
• Then I started to play with /boot/grub/grub.cfg file.
• After some trial and error, these below lines worked for me.
• menuentry 'win'{
  set root=(hd0,2)
  chainloader +1
  }
• I added above entry to the file mentioned above completely manually to the appropriate place. If you are following this then take a look at the file, examine it carefully and edit it accordingly.
1. using grub.d/xx_win stuff (I mention this because chances are good you are gonna find such guides involving that online pretty easily, they didn't work for me) messes my configuration and makes me to start to recover the grub process all over again and again.
• That's it; now I have dual boot.

I am guessing I took a very rocky and long way to have a dual boot system, but you may be in my shoes and need some light. Therefore my post may help to your cause. Have a nice journey and dual boot.

Remember don't follow this post to have dual boot. It may only help if you are nearly exactly in my situation to begin with. There are, I believe, tons of easier and safer ways to have dual boot in the first place.

VirtualBox on Kali Linux, How To?

It's been ages since I write anything, but it was constantly in my mind that I was reminding myself "c'mon Ozgur you should write something on your blog, you have a blog. Write!"

Now is the time, it'll be a very quick step-by-step.

Recently my new hobby is testing pentest distros. Of course along the way I know now some of my neighbours Wi-Fi passwords. After testing and trying out versions and configurations and drivers and CUDA and some other stuff, I think I am gonna settle on either Kali or WeakNetLabs. I can make Ubuntu an OK degree pentest distro as best of my abilities also, but I claimed it impossible to enable CUDA with my hardware. It will simply not be happening. I tried everything I know and can be found on forums and stuff. It will not work. So I continued...

WNL comes with CUDA 5.0 and pretty recent and decent Nvidia drivers out of box but I have some little other issues I first need to fix so it will take another post to go that way.

On the other hand, Kali is playing well with my hardware if I use Cuda 4.x and old Nvidia drivers. Which, frankly, I am ok with. Normally I update everything to the latest but in this case I will make an exception since it is really too hard to get it done everything correctly for me (which I mean WPA cracking via CUDA =P ).

Back to the guide; I will try to give you little heads up before you use Kali as a host for VirtualBox images. I will assume you login as root and since it is a pentest distro you should be familiar with most of the stuff already.

apt-get update

if you have still 2 or 3 lines of  sources.list after this, it is a good time to find an appropriate sources.list for your distro which Kali I hope not BackTrack.

apt-get install linux-headers-`uname -r`

this should update 20 to 60 mbs if not it is probably because of the sources.list is not rich enough. You may get some errors like cannot locate 37-trunk-amd64 or such with header update, but it is a matter of fixing the sources.list really.

after that we should head to the https://www.virtualbox.org and press downloads. You should see the version and platforms. Find and click
VirtualBox 4.x.yz for Linux hosts on. You will not see anything close to our distro. But you can very easily locate the last one;
All distributions choose your platform, either 32 or 64 bits. Download the file, I am assuming you download it to the ~/Downloads/. Following finishing download make the file executable with chmod and then run it.

chmod +x VirtualBox-4.2.16-86992-Linux_amd64.run

./VirtualBox-4.2.16-86992-Linux_amd64.run

what you should see if everything goes right is;

 Verifying archive integrity... All good.
Uncompressing VirtualBox for Linux installation............
VirtualBox Version 4.2.16 r86992 (2013-07-04T14:33:09Z) installer
Installing VirtualBox to /opt/VirtualBox
Python found: python, installing bindings...
Building the VirtualBox kernel modules

VirtualBox has been installed successfully.

You will find useful information about using VirtualBox in the user manual
  /opt/VirtualBox/UserManual.pdf
and in the user FAQ
  http://www.virtualbox.org/wiki/User_FAQ

We hope that you enjoy using VirtualBox.

after that type and go the default installation directory;

cd /opt/VirtualBox/

get a list there. You will see a VirtualBox executable righted file. Run it directly from the console.

VirtualBox

Voilà!

There you have your VirtualBox on Kali.

I tried also XP on it and it worked just as fine without any hassle. It's a good setting now. CUDA to crack and i3 CPU - 8GB ram to play with.

Enjoy. Next time I will write about qbittorrent application and its nicest settings I figured out for Kali or maybe on WeakNetLabs.