Enjoy Backtrack 4 even more...with Fluxbox!!!

If your here you obviously want to get your Flux on in Backtrack 4. When the developers didn't incorporate Fluxbox into Backtrack 4 I was bummed, but understood their reasoning. While most everyone is just fine using KDE as a window manager in Backtrack 4, I prefer a more light weight and fast window manager like Fluxbox to do my auditing and testing in. With all that being said, I'll now show you how to install Fluxbox in just a few easy steps.


Step 1.
Well the first thing your going to have to do is install Fluxbox, but first lets make sure your system is up to date. Open a shell and type:

apt-get update && apt-get upgrade

Once the updates finish downloading and installing (if any) in the same shell type:

apt-get install fluxbox

This will install everything we need to start using Fluxbox.


Step 2.
Now, log out of your KDE session and in your tty1 session type:

echo "exec startfluxbox" > ~/.xinitrc

What this command does is add the line "exec startfluxbox" to your ~/.xinitrc file. This determines what window manager loads when you type "startx".


Step 3.
Now for the fun part, in your tty1 session type:

startx

Fluxbox, right? If you ever used Fluxbox before you know to access the menu you need to right click the desktop....but whats this!?! All your menu items....they're gone!?! Not to fear my fellow minimalists, I had a good couple weeks to type you guys up a whole custom Fluxbox menu especially for Backtrack 4. You can download the custom menu file here. When you are prompted to choose a location for the file to download to, download it to:

~/.fluxbox/

You will then be prompted again that a file named "menu" already exists, click replace to replace to old menu file with the new one. If it downloads to another location you need to move it to the ~/.fluxbox/ directory or it will not work! Alright, did you notice when you right click the desktop your menu is different? Everything from the KDE version of the menu is included and in the same spots, so you wont have to do any searching for tools.


Step 4.
But wait, nothing automatically starts up in Fluxbox like it did in KDE? There is a simple fix for that problem. Open a shell and type:

cd .fluxbox/ && nano startup

This will start a nano session. The Fluxbox startup script has lots of options you can mess around with, but we need to scroll down to the bottom until you see:

# Applications you want to start with fluxbox.
# MAKE SURE THAT APPS THAT KEEP RUNNING HAVE AN "&" AT THE END.
#
# unclutter -idle 2 &
# wmnd &
# wmsmixer -w &
# idesk &

What we want to do here is erase the four commented out entries and add our own, for instance:

# Applications you want to start with fluxbox.
# MAKE SURE THAT APPS THAT KEEP RUNNING HAVE AN "&" AT THE END.
#
wicd-client &
/opt/kde3/bin/kmix &
/opt/kde3/bin/kpowersave &

This will start three things when Fluxbox starts, Wicd Network Manager, Kmix, and Kpowersave.


And that's it! Aside from configuring Fluxbox how you like, your set. Pretty easy, right? You can now enjoy Backtrack 4 through a different, more light weight window manger.

Please post any feedback or questions you may have, thanks for reading!

How to Start Networking in Backtrack

How to Start Networking in Backtrack



This is always a huge topic and it seems simple to many of us but the fact of the matter is we have a lot of "new" people so we need to be clear about this sort of thing. (Note all commands should be run as root or with sudo)

1. To start networking in Backtrack 4 final issue the following command.

/etc/init.d/networking start

This will attempt to start all the interfaces in the /etc/network/interfaces file.

root@bt:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto eth1
iface eth1 inet dhcp

auto eth2
iface eth2 inet dhcp

auto ath0
iface ath0 inet dhcp

auto wlan0
iface wlan0 inet dhcp


If you don't have or don't want some of these interfaces then simply remove the from this file and they will not start.

If you need to set a static IP just set the variables in the /etc/network/interfaces file

auto eth0
iface eth0 inet static
address 192.168.0.100
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.1

You will also need to make sure you set a nameserver in /etc/resolv.conf

root@bt:~# cat /etc/resolv.conf
nameserver 192.168.0.1

So for example if all you have is eth0 and wlan0 on your system and you want them both to get a adress via DHCP then remove every thing else for the file with the exception of the lo interface. Here is a example.

root@bt:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp


Now if are lazy and want all this to start at boot you can simply issue this command as root

update-rc.d networking defaults

This will create all the proper sym-links

What about ssh?

So while I am on the subject I may as well go over ssh. In order to use ssh on backtrack 4 final you need to generate the keys first.

sshd-generate

after that you can start ssh like this:

/etc/init.d/ssh start

or you can add it to the boot sequence like this:

update-rc.d ssh defaults

Well thats enough to get up and running. I hope this was somewhat helpful to any one just getting started with backtrack.,

HowTo Install Immunity Debugger by Wine

Lightbulb HowTo Install Immunity Debugger by Wine

link for download:
IMMUNITY : Knowing You're Secure

News
IMMUNITY : Knowing You're Secure

Immunity Debugger is a powerful new way to write exploits, analyze malware, and reverse engineer binary files. It builds on a solid user interface with function graphing, the industry's first heap analysis tool built specifically for heap creation, and a large and well supported Python API for easy extensibility.

* A debugger with functionality designed specifically for the security industry
* Cuts exploit development time by 50%
* Simple, understandable interfaces
* Robust and powerful scripting language for automating intelligent debugging
* Lightweight and fast debugging to prevent corruption during complex analysis
* Connectivity to fuzzers and exploit development tools


The Best of Both Worlds
Immunity Debugger's interfaces include the GUI and a command line. The command line is always available at the bottom of the GUI. It allows the user to type shortcuts as if they were in a typical text-based debugger, such as WinDBG or GDB. Immunity has implemented aliases to ensure that your WinDBG users do not have to be retrained and will get the full productivity boost that comes from the best debugger interface on the market.

Commands can be extended in Python as well, or run from the menu-bar.

HowTo Install Immunity Debugger by Wine

Step 1
Create folders in:

/pentest/re/immunity_debugger

Step 2a
Click in file:
ImmunityDebugger_1_73_setup.exe

Step 2b
Click in "I Agree"

Step 3
Click in "Install" and use Path C:\Program Files\Immunity Inc\Immunity Debugger

Step 4
Download Python 2.7 Release

Step 5
Execute shell:
#wine msiexec /i python-2.7.msi

Step 6
Option "Install for all users"

C:\Python27\
next, next, next and Finish

Step 7
Delete desktop icon "Immunity Debugger"

Step 8
- Click "Dragon Icon" right click and click "Menu Editor"
- Move Menu "Wine->Programs->Immunity Inc->" to "Backtrack"->Reverse Engineering""

Step 9
Save "menu editor" File->Save

Step 10
Click "Dragon Icon"->"Backtrack"->"Reverse Engineering"->"Immunity Inc"->"Immunity Debugger"->"Immunity Debugger"

Happy Exploits, Shellcodes, Nops:)

@firebitsbr