April « 2009 « Longjidin's Kg Lengkong to Bukit Lada

Dual Boot BackTrack with Windows Xp

Posted in BackTrack by longjidin on April 27, 2009

What you need
Computer with Win XP Or vista or other OS installed
BackTrack 3 Final iso on a CD or DVD or USB stick to boot from

Backup
Back up your entire system, there is no guarantee that it will not break.

Defrag your XP NTFS partition
While still in Win XP, defrag your NTFS drive. You will resize it to make space for the BackTrack partitions.

Boot BackTrack live from CD, DVD or USB device
Unmount the existing partitions, the BackTrack Live has automatically mounted them.

umount /dev/sda1
umount /dev/sda2

Run QTParted to resize the NTFS partition
KDE menu > System > QTParted
Resize sda1 to make free space for BackTrack and save changes. Exit QTParted.

Create Linux partitions for BackTrack
fdisk /dev/sda

Create a primary partition number sda3 1 GB in size, this will be swap
Create a primary partition number sda4 of remaining space, this will be /boot and /
Format the new partitions
mkfs.ext3 /dev/sda4
mkswap /dev/sda3
swapon /dev/sda3

Mount the new partitions so you can install BackTrack on them
bt ~ # mkdir /mnt/backtrack
bt ~ # mount /dev/sda4 /mnt/backtrack/
bt ~ # mkdir /mnt/backtrack/boot/
bt ~ # mount /dev/sda4 /mnt/backtrack/boot/

Install BackTrack files
bt ~ # cp –preserve -R /{bin,dev,home,pentest,root,usr,etc,lib,opt,sbin,var} /mnt/backtrack/
bt ~ # mkdir /mnt/backtrack/{mnt,proc,sys,tmp}
bt ~ # mount –bind /dev/ /mnt/backtrack/dev/
bt ~ # mount -t proc proc /mnt/backtrack/proc/
bt ~ # cp /boot/vmlinuz /mnt/backtrack/boot/

And lilo file
bt ~ # chroot /mnt/backtrack/ /bin/bash
bt / # nano /etc/lilo.conf
In nano change the line at the lilo file
1. boot /dev/sda or boot /dev/hda
2.timeout=60
3.root = /dev/sda4
4.remove read-only
5.add the following line at the end of the lilo file
other=/dev/sda1
label=Windows
Excellent. Save that and then execute lilo
bt / # lilo -v
after that exit your chroot enviorment
and reboot and cross your fingers
bt / # exit
bt ~ #reboot

Good Day Mate!!!!…… :>

longjidin

Lenovo ThinkPad T60p, Intel Centrino Dua Core. 1 GB RAM, ATI Technologies Inc M56GL, Atheros Communications, Inc. AR5212/AR5213 Multiprotocol

Thanks to ao255 for this tutorial : http://forums.remote-exploit.org/archive/index.php/t-16806.html

Tagged with: dual boot Bt with XP

Backtrack 3 and Intel’s 3945ABG wireless card Injection

Posted in BackTrack by longjidin on April 25, 2009

Having seen so many people in #remote-exploit trying their best to get Backtrack 3 working with Intel’s wireless chipsets, mainly the 3945ABG, I decided to write a quick-howto. Lets start by saying it’s not quite easy. The default driver for Intel 3945 chipsets can do normal wireless stuff, but can’t inject. The injection driver can’t do normal wireless stuff. So you have to pick your tasks, and thus which driver to use, carefully.In this brief guide I’ll show you the quick way of getting over to the injection driver, finding a network in kismet and throwing wesside-ng at it to obtain the key. Then I’ll show how to swap back over and connect to the network you’ve just pen-tested.

So, how do you know this guide is for you? A nice quick way is to do

Code: Select all: lspci | grep 3945ABG

You’ll get something like:

Code: Select all: 02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

If so, move on, you’re doing well.

The first thing to note is that the default driver for this card is called `iwl3945`. Using an `iwconfig` will get you something like:

airmon-ng tells us:

Code: Select all

Interface Chipset Driver

wlan0 iwl3945 – [phy0]

If you were to try tell airmon-ng to enable monitor mode on wlan0, you’d get an error like:

Code: Select all: /usr/local/sbin/airmon-ng: line 338: /sys/class/ieee80211/phy0/add_iface: Permission denied mon0: ERROR while getting interface flags: No such device

So you need to do the following:

Code: Select all: # modprobe -r iwl3945 # modprobe ipwraw

Then do an iwconfig, and you’ll see this…

This wifi0 device can go into monitor mode:

Now to find your network to pen-test (and of course, only do this on hardware you own. In this case we’re going to use the BT Home Hub we have here).

First edit /usr/local/etc/kismet.conf in you fave editor. We’re only going to change a single line, so no need to load anything fancy (I myself use nano, but use what you’d like)

Scroll down to the “source=” line. You’ll want to alter the source line to read something like:

Code: Select all: source=iwl3945,wifi0,Intel

Save your changes, and start kismet. Find the network you’re looking for (pressing ’s’ and then ‘f’ for first-seen sort order), then press ‘i’ to get the following info:

Note down the MAC address of the router, exit kismet.

Now the fun part. wesside-ng takes the tedious work out of getting all the IV packets and running aircrack-ng on them to get the key. To use wesside-ng:

Code: Select all: wesside-ng -i wifi0 -v {BSSID}

In our case, we’ll put in the BSSID of the target network, 00:14:7F:A1:97:39.

Here’s wesside-ng after successful authentication:

Here we’re cracking the key:

Tada, it found the test key, E723F7D5E8 (Yes, it’s a 64-bit key for speed and testing).

Now we need to prove this is correct. Reverse the drivers:

Code: Select all: # modprobe -r ipwraw # modprobe iwl3945

Fire up your chosen network finder (The wireless assistant will suffice here), find the network in question and click “connect”. Enter in the key we just found.

There we go, success: