How to Create You Lab on Kali Linux - Using VMware or VBox

Before you start - Here are something that you need to consider..

• Install VirtualBox or Vmware
• Install LiveCD in VirtualBox or Vmware
• Boot and try out your LiveCD

Introduction.


There are lots of tutorials available on the internet related to hacking but the big problem lies in testing your theoretical skills. Unless you don't have practical exposure to hacking, you cannot really understand the strength of it. The technique I will discuss here will be advantageous for those who have only single system and want to set up a testing network using it. In case you have multiple systems then you can easily test for your skills by making one system as target and other as attacker.

VMware Workstation 12 Pro - Leading Edge PC Virtualization VMware Workstation 12 Pro

Download VMware Workstation or Player

The best way to practice hacking is within a virtual environment. Essentially, you set up a hacking system, such as Kali Linux, and some victims to exploit. Ideally, you would want multiple operating systems (Windows XP, Vista, 7, and 8, as well as a Linux flavor) and applications so that you can try out a variety of hacks.

Virtual machines and a virtual network are the best and safest way to set up a hacking lab. There are several virtualization systems out there, including Citrix, Oracle's VirtualBox, KVM, Microsoft's Virtual PC and Hyper-V, and VMware'sWorkstation, VMware Player and ESXi. For a laboratory environment, I strongly recommend VMware's Workstation or Player. Workstation is commercial product that costs under $200, while Player is free. You can also get a free 30-day trial of Workstation.

Player is limited to just playing VMs , while Workstation can both create and play VMs. Let's download VMware's Workstation or Player here.

Then - For you Images you can download a pre-built image. As it will allow you to save some time, you don't need to build the image from scratch. Here is a link for you to download several Linux pre-built Linux Images on SourceForge.

I don't encourage you to download pre-built Windows VM from anywhere, for the single fact that Microsoft itself provides you with pre-built Windows VM for you to use on your VM Lab. Again I did the research for you and here it the link for you to download the Windows of your choice,  Obs: Remember Windows only allow you to use those VM images for 30 days. Please, READ Microsoft TERMS AND CONDITIONS before you use their software here is the url for you.



Keep posted - This tutorial continues on Part 2

Also check this Handful tutorials I have found online:

Checkout our tutorial videos below. Learn more about.

1. OWASP AppSec Basics: http://www.youtube.com/watch?v=CDbWvEwBBxo
2. OWASP SQL Injection: http://www.youtube.com/watch?v=pypTYPaU7mM
3. OWASP Cross Site Scripting: http://www.youtube.com/watch?v=_Z9RQSnf8-g
4. OWASP Strict Transport Security: http://www.youtube.com/watch?v=zEV3HOuM_Vw

How to Use Microsoft Ready-Made VM Images for VMware and VBox

Microsoft Officially Offering Ready-Made VirtualBox And VMWare Images

Microsoft Offering ready made pre-installed windows operating system to test Internet Explorer  , virtual machine images are available for windows ,mac and linux virtualization solutions , for cross browser testing , so you can test your site in different operating systems .

IE versions being offered are:

• IE7 on Vista
• IE8 on Windows 7
• IE9 on Windows 7
• IE10 on Windows 8

Offered  VMs that will run on:

• Windows
• OSX
• Linux

The VM software choices are specific to the OS you choose:

• Windows – Hyper-V, Virtual PC, VirtualBox & VMWare Player
• OSX- VirtualBox & VMWare Fusion
• Linux – VirtualBox

Cross-browser testing
simplified

You have to just download and open vbox files with virtualbox or vmx files with vmware and you will get all pre-installed windows operating system , and you are good to go ,
there is pre-installed windows 8 virtual image if you want to test drive windows 8 🙂

How to Install virtual images :

1. Download Virtual Images
2. extract it somehwhere
3. open vmware player or workstation
4. click on file >> open
5. locate  ” somefile”.vmx
6. it will load up virtual image component

How the Internet Works ..Explained Here

Learn how to build a desktop computer or PC

Learn how to build your own computer or PC.  Allows you to customize to meet your exact needs!  Sorry the quality is a little bit crappy.

Parts...
Cooler Master Elite 310 Case
Asus P5Q SE Plus motherboard
Intel Quad core Q8200 2.33 GHZ 4 MB cache 1333 MHZ FSB
Kingston PC8500 2 GB RAM 1066 MHZ
XFX GeForce 9800 GT 512MB GDDR3
Samsung 500 GB SATA HD 7200 RPM 16 MB buffer
Antec 500 W power supply
Samsung 22x SATA dual layer DVD burner
2x Antec 120mm ball bearing multiple speed fans

Music by:  incompetech.com
Song: Deliberate Thought
For use under Creative Commons license 3.0

VMware Workstation 8.0.2 does not Work with uBuntu 12.04 LTS

Hi there ...

About some day ago, I have updated my system,

I'have created this post to share, the way I have troubleshoot and successfully update the Linux Kernel make VMware Workstation 8.0.2 work and Kubuntu 12.04..

Installing VMware 8.0.2 64bit

Ubuntu 12.04LTS 64bit BETA

My Kernel version is: 3.2.0-20-generic

pst007x@pst007x-Aspire-5741:~$ sudo sh VMware-Workstation-Full-8.0.2- 591240.x86_64.bundle

Installs ok

When I launch I am asked to install modules which are compiled and loaded into the running kernel.

A window opens

VMware Kernel Module Updater

This fails on Virtual Network Device

ERROR LOG.

UPDATE:

PATCH.

When I try to add patch, following error:

 pst007x@pst007x-Aspire-5741:~$ sudo sh patch-modules_3.2.0.sh
 [sudo] password for pst007x: 
 patch-modules_3.2.0.sh: 27: [: workstation8.0.2: unexpected operator
 patch-modules_3.2.0.sh: 28: [: workstation8.0.2: unexpected operator
 Sorry, this script is only for VMWare WorkStation 8.0.2 or VMWare Player 4.0.2. 
 Exiting
 pst007x@pst007x-Aspire-5741:~$

I have fully un-installed, and re-installed. I am installing the correct version. Probably a problem with the patch. VMware installs perfectly on Ubuntu 11.10..

.. Here is how I've worked it out .. 

Move to Home folder

1. VMware-Workstation-Full-8.0.2-591240.x86_64.bundle
2. PATCH: patch-modules_3.2.0.sh
3. PATCH: vmware3.2.0.patch

Patch download link (xtact contents to Home folder):

http://weltall.heliohost.org/wordpress/2012/01/26/vmware-workstation-8-0-2-player-4-0-2-fix-for-linux-kernel-3-2-and-3-3/

"root@mukonda:/home/malange/Downloads# sudo  sh VMware-Workstation-Full-8.0.2-i386.bundleExtracting VMware Installer...done.
No protocol specified
No protocol specified
No protocol specified
No protocol specified

You must accept the VMware OVF Tool component for Linux End UserLicense Agreement to continue.  Press Enter to proceed.
                                                
VMWARE OPEN VIRTUALIZATION FORMAT TOOL LICENSE AGREEMENTNotice to User:This Open Virtualization Format Tool ("OVF Tool") License Agreement is a ... "bla bla bla "


Here is the Ubuntu Terminal Log record ...

"root@kubata:/home/malange/Downloads# ./patch-modules_3.2.0.sh                                                                                                                
-bash: ./patch-modules_3.2.0.sh: Permission denied                                                                                                                                  
root@kubata:/home/malange/Downloads# ./patch-modules_3.2.0.sh                                                                                                                      
patching file vmnet-only/filter.c                                                                                                                                                   
patching file vmnet-only/netif.c                                                                                                                                                    
patching file vmnet-only/userif.c                                                                                                                                                   
Stopping VMware services:                                                                                                                                                           
   VMware Authentication Daemon                                        done                                                                                                         
   VM communication interface socket family                            done                                                                                                         
   Virtual machine communication interface                             done                                                                                                         
   Virtual machine monitor                                             done                                                                                                         
   Blocking file system                                                done                                                                                                         
Using 2.6.x kernel build system.                                                                                                                                                    
make: Entering directory `/tmp/vmware-root/modules/vmmon-only'                                                                                                                      
make -C /lib/modules/3.2.0-24-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \                                                                                            
          MODULEBUILDDIR= modules                                                                                                                                                   
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driver.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/driverLog.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/linux/hostif.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/apic.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/comport.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/cpuid.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/hashFunc.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/memtrack.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/phystrack.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/task.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/common/vmx86.o
  CC [M]  /tmp/vmware-root/modules/vmmon-only/vmcore/moduleloop.o
  LD [M]  /tmp/vmware-root/modules/vmmon-only/vmmon.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmmon-only/vmmon.mod.o
  LD [M]  /tmp/vmware-root/modules/vmmon-only/vmmon.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmmon-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
cp -f vmmon.ko ./../vmmon.o
make: Leaving directory `/tmp/vmware-root/modules/vmmon-only'
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Built vmmon module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make -C /lib/modules/3.2.0-24-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
  CC [M]  /tmp/vmware-root/modules/vmnet-only/driver.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/hub.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/userif.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/netif.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/bridge.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/filter.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/procfs.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/smac_compat.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/smac.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/vnetEvent.o
  CC [M]  /tmp/vmware-root/modules/vmnet-only/vnetUserListener.o
  LD [M]  /tmp/vmware-root/modules/vmnet-only/vmnet.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmnet-only/vmnet.mod.o
  LD [M]  /tmp/vmware-root/modules/vmnet-only/vmnet.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmnet-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
cp -f vmnet.ko ./../vmnet.o
make: Leaving directory `/tmp/vmware-root/modules/vmnet-only'
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Built vmnet module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make -C /lib/modules/3.2.0-24-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/block.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/control.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/dbllnklst.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/dentry.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/file.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/filesystem.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/inode.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/module.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/stubs.o
  CC [M]  /tmp/vmware-root/modules/vmblock-only/linux/super.o
  LD [M]  /tmp/vmware-root/modules/vmblock-only/vmblock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmblock-only/vmblock.mod.o
  LD [M]  /tmp/vmware-root/modules/vmblock-only/vmblock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmblock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
cp -f vmblock.ko ./../vmblock.o
make: Leaving directory `/tmp/vmware-root/modules/vmblock-only'
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Built vmblock module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vmci-only'
make -C /lib/modules/3.2.0-24-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/driver.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/linux/vmciKernelIf.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciContext.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDatagram.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDoorbell.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciDriver.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciHashtable.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciEvent.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQPair.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciQueuePair.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciResource.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/common/vmciRoute.o
  CC [M]  /tmp/vmware-root/modules/vmci-only/driverLog.o
  LD [M]  /tmp/vmware-root/modules/vmci-only/vmci.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vmci-only/vmci.mod.o
  LD [M]  /tmp/vmware-root/modules/vmci-only/vmci.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vmci-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vmci-only'
cp -f vmci.ko ./../vmci.o
make: Leaving directory `/tmp/vmware-root/modules/vmci-only'
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Built vmci module
Using 2.6.x kernel build system.
make: Entering directory `/tmp/vmware-root/modules/vsock-only'
make -C /lib/modules/3.2.0-24-generic-pae/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= modules
make[1]: Entering directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/af_vsock.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/notify.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/notifyQState.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/stats.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/util.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/linux/vsockAddr.o
  CC [M]  /tmp/vmware-root/modules/vsock-only/driverLog.o
  LD [M]  /tmp/vmware-root/modules/vsock-only/vsock.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC      /tmp/vmware-root/modules/vsock-only/vsock.mod.o
  LD [M]  /tmp/vmware-root/modules/vsock-only/vsock.ko
make[1]: Leaving directory `/usr/src/linux-headers-3.2.0-24-generic-pae'
make -C $PWD SRCROOT=$PWD/. \
          MODULEBUILDDIR= postbuild
make[1]: Entering directory `/tmp/vmware-root/modules/vsock-only'
make[1]: `postbuild' is up to date.
make[1]: Leaving directory `/tmp/vmware-root/modules/vsock-only'
cp -f vsock.ko ./../vsock.o
make: Leaving directory `/tmp/vmware-root/modules/vsock-only'
No protocol specified
No protocol specified
No protocol specified
No protocol specified
Built vsock module
Starting VMware services:
   Virtual machine monitor                                             done
   Virtual machine communication interface                             done
   VM communication interface socket family                            done
   Blocking file system                                                done
   Virtual ethernet                                                    done
   VMware Authentication Daemon                                        done
   Shared Memory Available                                             done


All done, you can now run .
Modules sources backup can be found in the '/usr/lib/vmware/modules/source-workstation8.0.2-2012-05-21-
kubata@kubata:/home/malange/Downloads# 
"

Now here it VMware Working ... :-) 

                                                                                             Snapshot 1....

Snapshot 2 ....

This is another posting showing "how to do computing" for everyday computer usages... For a general public