| Filename | BackTrack - Penetration Testing Distribution Setting Part II |
| Permission | rw-r--r-- |
| Author | WhySoSeriousssssssssssss |
| Date and Time | 02:01 |
| Label | hack |
| Action |
There is a script to start the wicd-daemon in the /etc/init.d directory. To start it issue the following command:
root@bt:~# /etc/init.d/wicd start
This should be started before attempting to open the client. Once you have started the daemon you can open the GUI interface for the client from the KDE menu:
KDE > Internet > Wicd Network Manager
If you would like to have the Wic Daemon start at boot time:
root@bt:~# update-rc.d wicd defaults
Changing the root password
It is vital you change your root password before you open up any services, such as SSH. Make sure to change your default toor password!
root@bt:~# passwd
Enter new UNIX password: {enter your new password here }
Retype new UNIX password: {enter your new password again}
passwd: password updated successfully
root@bt:~#
Starting services
BackTrack has various services such as Apache, SSH, MySQL, VNC, etc. They are all disabled by default. To start a service such as SSH, you can use the service init scripts. For example, to start the SSH service:
root@bt:~# sshd-generate # Specific to the SSH service - needed to generate SSH keys
root@bt:~# /etc/init.d/ssh start
Starting OpenBSD Secure Shell server: sshd.
root@bt:~# /etc/init.d/ssh stop
Stopping OpenBSD Secure Shell server: sshd.
root@bt:~#
When using a ssh server for the first time on Backtrack you will need to generate keys:
root@bt:~# sshd-generate
To enable a service at boot time, you can use the update-rc.d command, for example, having SSH start at boot time:
root@bt:~# update-rc.d -f ssh defaults
Adding system startup for /etc/init.d/ssh ...
/etc/rc0.d/K20ssh -> ../init.d/ssh
/etc/rc1.d/K20ssh -> ../init.d/ssh
/etc/rc6.d/K20ssh -> ../init.d/ssh
/etc/rc2.d/S20ssh -> ../init.d/ssh
/etc/rc3.d/S20ssh -> ../init.d/ssh
/etc/rc4.d/S20ssh -> ../init.d/ssh
/etc/rc5.d/S20ssh -> ../init.d/ssh
root@bt:~#
Common apt commands
apt-get install (package) Downloads (package) and all of its dependencies, and installs or upgra- des them.
apt-get remove [--purge] (package) Removes (package) and any packages that depend on it.
apt-get update Updates packages listings from the repo, should be run at least once a week.
apt-get upgrade Upgrades all currently installed packages with those updates available from the repo.
apt-get dist-upgrade [-u] Similar to apt-get upgrade, except that dist-upgrade will install or remove packages to satisfy dependencies.
apt-cache search (pattern) Searches packages and descriptions for (pattern).
apt-cache show (package) Shows the full description of (package).
apt-cache showpkg(package) Shows a lot more detail about (package), and its relationships to other packages.
man apt Will give you more info on these commands as well as many that are in less common usage.
Common dpkg commands
dpkg -i (package.deb) Installs a package file; one that you downloaded manually, for example.
dpkg -c (package.deb) Lists the contents of (package.deb) a .deb file.
dpkg -I (package.deb) Extracts package information from (package.deb) a .deb file.
dpkg -r (package) Removes an installed package named (package)
dpkg -P (package) Purges an installed package named (package). The difference between remove and purge is that while remove only deletes data and executables, purge also deletes all configuration files in addition.
dpkg -L (package) Gives a listing of all the files installed by (package). See also dpkg -c for checking the contents of a .deb file.
dpkg -s (package) Shows information on the installed package (package). See also apt-cache show for viewing package information in the Debian archive and dpkg -I for viewing package information extracted from a .deb file.
dpkg-reconfigure (package) Reconfigures an installed package.
man dpkg Will give you more info on these commands as well as many that are in less common usage.
How do I find more information on a particular command or programs usage ?
Most commands will have what is called a man page (manual page) which can be viewed by typing:
root@bt:~# man (command you want more info on)
Another very good resource on linux command usage can be found at linuxcommand.org Some programs do not have a man page, but you can usually get more information on it's usage by typing:
root@bt:~# (program name) Just the program name without any arguements.
or
root@bt:~# (program name) -help
or
root@bt:~# (program name) --help
or
root@bt:~# (program name) -h
Wireless Drivers
With the ever changing arena of the wireless driver world and the mac80211 stack, we wanted to dedicate a page that would sort out some tricky wireless driver setups. Before you start your journey into BackTrack wireless world, you should first identify your wireless card chipset with 100% cer- tainty. If in doubt, you can always try plugging in the card into a Linux box, and see what dmesg has to say.
BackTrack contains patched stock kernel 2.6.35.8 wireless drivers, as well as several "external" drivers. Some of these drivers overlap, to provide maximum flexibility with various wireless attacks. The /etc/modprobe.d/blacklist dictates which preferred drivers are loaded at boot-time. Generally speaking, all the older IEEE drivers are blacklisted and need to be loaded manually if you want to use them.
Wireless Drivers
rtl8187 vs r8187
This is a confusing one. The rtl8187 is the mac80211 stack driver, while the r8187 is the old IEEE driver. Both support injection.
b43 vs wl
This is a nasty one. b43 supports only *some* broadcom cards. Make sure you know what card version you have before you get frustrated. Check the b43 compatibility list. Some Broadcom chipsets which are NOT covered by b43, *are* covered by the broadcom-STA driver(wl). Note that the wl driver does not support injection! People with macs, or unsupprted b43 broadcom cards such as the BCM4322 802.11a/b/g/n Wireless LAN, check out the broadcom wl page.
ath5k vs ath_pci
These drivers are for certain atheros cards - they should be interchangeable, and both support wireless injection.
compat wireless
As Linux wireless drivers mature, more chipsets get added to the compatibility list. If none of the native BackTrack kernel drivers work for you, you might want to consider using a more recent version of compat-wireless. Check out the compat-wireless page for information on how to get those drivers up and running.
Continue Part III here
0 comments:
Post a Comment