首先什么是Back track（简称bt）呢？引用一篇博客中的简介，让大家了解一下bt吧
http://www.pczpg.com/a/2010/0402/5445.html
BT4全称Back Track four，这是一个linux环境的便携系统，可以放到U盘或者光盘中启动，对本身硬盘没有影响，无需在本地安装
是圈内非常著名的黑客攻击平台，是一个封装好的Linux操作系统，内置大量的网络安全检测工具以及黑客破解软件等。
BT3~4因可以方便的破解无线网络而出名，其中内置的spoonwep是一个非常强悍的图形化破解WEP无线网络密码的工具。
Backtrack 是处于世界领先地位的渗透测试和信息安全审计发行版本。有着上百种预先安装好的工具软件，并确定能够
完美运行，Backtrack4 提供了一个强大的渗透测试平台--从Web hack的应用程序到RFID 审查，都可由Backtrack来完成。
内幕
BackTrack 的基础
BT4 引入了许多显著的变化，基于Ubuntu Intrepid。现在开始使用我们自己修改了的Ubuntu软件包和渗透测试工具软件来
维护我们自己全部的软件仓库。
另外一个显著的变化是更新linux 核心版本到2.6.29.4.这个新核心带来了一整套系统内在的变化，使得极大地改变了BackTrack
的架构。
Backtrack 的核心
不再使用lzma格式的squashfs作为live cd的文件系统，从而导致了一个更大容量的ISO文件。但从另外一个方面来看，这也使得我们
不用维护我们自己的核心补丁问题。目前这是很痛苦的，因为squashfs融入主流核心的速度十分缓慢。
BT4使用了squashfs-tools version 4.0,内建的squashfs核心模块（2.6.29.4），和旧版本不兼容。使用了AUFS格式作为
统一文件系统 （unification filesystem）。
核心已经安装了几个无线驱动的注入和优化补丁，并且打了bootsplash 补丁，这些补丁都能在核心源码包中找到。（/usr/src/linux/patches）
这些变化意味着以前很多在BT2/BT3中使用的方法已经不再有效，比如启动时的cheatcodes参数。
由于核心的转移也意味着不再使用live-linux脚本来生成iso文件，现在我们使用casper.
软件包和软件仓库
BT4中一个最大的变化就是使用了软件仓库，可以经常更新安全补丁和工具，类似Debian。意味着如果你选择把BT4安装到硬盘，
你就可以通过apt-get命令，维护和更新你的软件包。
BT4工具软件有以下几个大类：
BackTrack-Enumeration
BackTrack-Tunneling
BackTrack-Bruteforce
BackTrack-Spoofing
BackTrack-Passwords
BackTrack-Wireless
BackTrack-Discovery
BackTrack-Cisco
BackTrack-Web Applicaitons
BackTrack-Forensics
BackTrack-Fuzzers
BackTrack-Bluetooth
BackTrack-Misc
BackTrack-Sniffers
BackTrack-VOIP
BackTrack-Debuggers
BackTrack-Penetration
BackTrack-Database
BackTrack-RFID
BackTrack-Python
BackTrack-Drivers
BackTrack-GPU
…………
以前其实接触过BT，但当时只是用虚拟机加载一番，看了看，什么也没弄，命令都不懂，现在学了一段时间的linux之后，玩弄一下BT其实也挺有趣的。
先是安装：
用虚拟机（或者刻录到光盘上去）加载后，运行，随便选择一种界面进入，然后输入startx
开始进入自带的bt系统，点击桌面上的install.sh，进入bt系统的安装界面
选择第一个，全盘覆盖安装，然后一直“Forward”
最后重启一下就安装完闭了，一开始默认的是root账户登陆，输入用户root，密码toor，这样就可以进入root命令行，输入startx，开始进入桌面。
联网：用命令 start-network
修改分辨率：下面是我修改后xorg.conf文件里的内容，修改里面的分辨率（一般是修改值为24的那个分辨率），然后把/etc/X11/xorg.conf覆盖就行了。
# File generated by xf86config. # # Copyright (c) 1999 by The XFree86 Project, Inc. # # Permission is hereby granted, free of charge, to any person obtaining a # copy of this software and associated documentation files (the "Software"), # to deal in the Software without restriction, including without limitation # the rights to use, copy, modify, merge, publish, distribute, sublicense, # and/or sell copies of the Software, and to permit persons to whom the # Software is furnished to do so, subject to the following conditions: # # The above copyright notice and this permission notice shall be included in # all copies or substantial portions of the Software. # # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL # THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, # WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF # OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE # SOFTWARE. # # Except as contained in this notice, the name of the XFree86 Project shall # not be used in advertising or otherwise to promote the sale, use or other # dealings in this Software without prior written authorization from the # XFree86 Project. # # ********************************************************************** # Refer to the XF86Config(4/5) man page for details about the format of # this file. # ********************************************************************** # NOTE: This is a NEW IMPROVED version of XF86Config-fbdev that uses the vesa # driver instead of the fbdev driver. Thanks to Kenneth Fanyo who pointed # this out to me. :) # This XF86Config file is designed for use with the VESA framebuffer. # This generic interface should work with nearly all video cards # (although not every card will support every resolution). # With the new driver, it should no longer be required to have frame buffer # support in the kernel, or to run it on the console. # # Enjoy! :) # -- [email protected] # # ********************************************************************** # Module section -- this section is used to specify # which dynamically loadable modules to load. # ********************************************************************** # Section "Module" # This loads the DBE extension module. Load "dbe" # Double buffer extension # This loads the miscellaneous extensions module, and disables # initialisation of the XFree86-DGA extension within that module. SubSection "extmod" Option "omit xfree86-dga" # don't initialise the DGA extension EndSubSection # This loads the font modules Load "type1" Load "freetype" #Load "speedo" # This loads the GLX module Load "glx" EndSection # ********************************************************************** # Files section. This allows default font and rgb paths to be set # ********************************************************************** Section "Files" # The location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. # Multiple FontPath entries are allowed (which are concatenated together), # as well as specifying multiple comma-separated entries in one FontPath # command (or a combination of both methods) # # If you don't have a floating point coprocessor and emacs, Mosaic or other # programs take long to start up, try moving the Type1 and Speedo directory # to the end of this list (or comment them out). # FontPath "/usr/X11R6/lib/X11/fonts/local/" FontPath "/usr/X11R6/lib/X11/fonts/misc/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1/" FontPath "/usr/X11R6/lib/X11/fonts/CID/" FontPath "/usr/X11R6/lib/X11/fonts/Speedo/" FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/" # ModulePath can be used to set a search path for the X server modules. # The default path is shown here. # ModulePath "/usr/X11R6/lib/modules" EndSection # ********************************************************************** # Server flags section. # ********************************************************************** Section "ServerFlags" # Uncomment this to cause a core dump at the spot where a signal is # received. This may leave the console in an unusable state, but may # provide a better stack trace in the core dump to aid in debugging # Option "NoTrapSignals" # Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence # (where n is 1 through 12). This allows clients to receive these key # events. # Option "DontVTSwitch" # Uncomment this to disable the <Crtl><Alt><BS> server abort sequence # This allows clients to receive this key event. # Option "DontZap" # Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching # sequences. This allows clients to receive these key events. # Option "DontZoom" # Uncomment this to disable tuning with the xvidtune client. With # it the client can still run and fetch card and monitor attributes, # but it will not be allowed to change them. If it tries it will # receive a protocol error. # Option "DisableVidModeExtension" # Uncomment this to enable the use of a non-local xvidtune client. # Option "AllowNonLocalXvidtune" # Uncomment this to disable dynamically modifying the input device # (mouse and keyboard) settings. # Option "DisableModInDev" # Uncomment this to enable the use of a non-local client to # change the keyboard or mouse settings (currently only xset). # Option "AllowNonLocalModInDev" # Set the basic blanking screen saver timeout. # Option "blank time" "10" # 10 minutes # Set the DPMS timeouts. These are set here because they are global # rather than screen-specific. These settings alone don't enable DPMS. # It is enabled per-screen (or per-monitor), and even then only when # the driver supports it. # Option "standby time" "20" # Option "suspend time" "30" # Option "off time" "60" # On some platform the server needs to estimate the sizes of PCI # memory and pio ranges. This is done by assuming that PCI ranges # don't overlap. Some broken BIOSes tend to set ranges of inactive # devices wrong. Here one can adjust how aggressive the assumptions # should be. Default is 0. # Option "EstimateSizesAggresively" "0" EndSection # ********************************************************************** # Input devices # ********************************************************************** # ********************************************************************** # Core keyboard's InputDevice section # ********************************************************************** Section "InputDevice" Identifier "Keyboard1" Driver "kbd" # For most OSs the protocol can be omitted (it defaults to "Standard"). # When using XQUEUE (only for SVR3 and SVR4, but not Solaris), # uncomment the following line. # Option "Protocol" "Xqueue" # Set the keyboard auto repeat parameters. Not all platforms implement # this. # Option "AutoRepeat" "500 5" # Specifiy which keyboard LEDs can be user-controlled (eg, with xset(1)). # Option "Xleds" "1 2 3" # To disable the XKEYBOARD extension, uncomment XkbDisable. # Option "XkbDisable" # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a European # keyboard, you will probably want to use one of: # # Option "XkbModel" "pc102" # Option "XkbModel" "pc105" # # If you have a Microsoft Natural keyboard, you can use: # # Option "XkbModel" "microsoft" # # If you have a US "windows" keyboard you will want: # # Option "XkbModel" "pc104" # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # # Option "XkbLayout" "de" # # or: # # Option "XkbLayout" "de" # Option "XkbVariant" "nodeadkeys" # # If you'd like to switch the positions of your capslock and # control keys, use: # # Option "XkbOptions" "ctrl:swapcaps" # These are the default XKB settings for X.Org # # Option "XkbRules" "xorg" # Option "XkbModel" "pc101" # Option "XkbLayout" "us" # Option "XkbVariant" "" # Option "XkbOptions" "" EndSection # ********************************************************************** # Core Pointer's InputDevice section # ********************************************************************** Section "InputDevice" # Identifier and driver Identifier "Mouse1" Driver "mouse" Option "ZAxisMapping" "4 5" Option "Buttons" "3" # On platforms where PnP mouse detection is supported the following # protocol setting can be used when using a newer PnP mouse: # Option "Protocol" "Auto" # The available mouse protocols types that you can set below are: # Auto BusMouse GlidePoint GlidePointPS/2 IntelliMouse IMPS/2 # Logitech Microsoft MMHitTab MMSeries Mouseman MouseManPlusPS/2 # MouseSystems NetMousePS/2 NetScrollPS/2 OSMouse PS/2 SysMouse # ThinkingMouse ThinkingMousePS/2 Xqueue Option "Protocol" "IMPS/2" # The mouse device. The device is normally set to /dev/mouse, # which is usually a symbolic link to the real device. Option "Device" "/dev/mouse" # Option "Device" "/dev/psaux" # Option "Device" "/dev/ttyS0" # Option "Device" "/dev/ttyS1" # When using XQUEUE, comment out the above two lines, and uncomment # the following line. # Option "Protocol" "Xqueue" # Baudrate and SampleRate are only for some Logitech mice. In # almost every case these lines should be omitted. # Option "BaudRate" "9600" # Option "SampleRate" "150" # Emulate3Buttons is an option for 2-button Microsoft mice # Emulate3Timeout is the timeout in milliseconds (default is 50ms) # Option "Emulate3Buttons" # Option "Emulate3Timeout" "50" # ChordMiddle is an option for some 3-button Logitech mice # Option "ChordMiddle" EndSection # Some examples of extended input devices # Section "InputDevice" # Identifier "spaceball" # Driver "magellan" # Option "Device" "/dev/cua0" # EndSection # # Section "InputDevice" # Identifier "spaceball2" # Driver "spaceorb" # Option "Device" "/dev/cua0" # EndSection # # Section "InputDevice" # Identifier "touchscreen0" # Driver "microtouch" # Option "Device" "/dev/ttyS0" # Option "MinX" "1412" # Option "MaxX" "15184" # Option "MinY" "15372" # Option "MaxY" "1230" # Option "ScreenNumber" "0" # Option "ReportingMode" "Scaled" # Option "ButtonNumber" "1" # Option "SendCoreEvents" # EndSection # # Section "InputDevice" # Identifier "touchscreen1" # Driver "elo2300" # Option "Device" "/dev/ttyS0" # Option "MinX" "231" # Option "MaxX" "3868" # Option "MinY" "3858" # Option "MaxY" "272" # Option "ScreenNumber" "0" # Option "ReportingMode" "Scaled" # Option "ButtonThreshold" "17" # Option "ButtonNumber" "1" # Option "SendCoreEvents" # EndSection # ********************************************************************** # Monitor section # ********************************************************************** # Any number of monitor sections may be present Section "Monitor" Identifier "My Monitor" # HorizSync is in kHz unless units are specified. # HorizSync may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. HorizSync 31.5 - 150.0 # HorizSync 30-64 # multisync # HorizSync 31.5, 35.2 # multiple fixed sync frequencies # HorizSync 15-25, 30-50 # multiple ranges of sync frequencies # VertRefresh is in Hz unless units are specified. # VertRefresh may be a comma separated list of discrete values, or a # comma separated list of ranges of values. # NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S # USER MANUAL FOR THE CORRECT NUMBERS. VertRefresh 75-85 EndSection # ********************************************************************** # Graphics device section # ********************************************************************** # Any number of graphics device sections may be present Section "Device" Identifier "VESA Framebuffer" Driver "vesa" #VideoRam 4096 # Insert Clocks lines here if appropriate EndSection # ********************************************************************** # Screen sections # ********************************************************************** # Any number of screen sections may be present. Each describes # the configuration of a single screen. A single specific screen section # may be specified from the X server command line with the "-screen" # option. Section "Screen" Identifier "Screen 1" Device "VESA Framebuffer" Monitor "My Monitor" # If your card can handle it, a higher default color depth (like 24 or 32) # is highly recommended. # DefaultDepth 8 # DefaultDepth 16 DefaultDepth 24 # DefaultDepth 32 # "1024x768" is also a conservative usable default resolution. If you # have a better monitor, feel free to try resolutions such as # "1152x864", "1280x1024", "1600x1200", and "1800x1400" (or whatever your # card/monitor can produce) Subsection "Display" Depth 8 Modes "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 24 Modes "1366x768" "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 32 Modes "1366x768" "1024x768" "800x600" "640x480" EndSubsection EndSection # ********************************************************************** # ServerLayout sections. # ********************************************************************** # Any number of ServerLayout sections may be present. Each describes # the way multiple screens are organised. A specific ServerLayout # section may be specified from the X server command line with the # "-layout" option. In the absence of this, the first section is used. # When now ServerLayout section is present, the first Screen section # is used alone. Section "ServerLayout" # The Identifier line must be present Identifier "Simple Layout" # Each Screen line specifies a Screen section name, and optionally # the relative position of other screens. The four names after # primary screen name are the screens to the top, bottom, left and right # of the primary screen. In this example, screen 2 is located to the # right of screen 1. Screen "Screen 1" # Each InputDevice line specifies an InputDevice section name and # optionally some options to specify the way the device is to be # used. Those options include "CorePointer", "CoreKeyboard" and # "SendCoreEvents". InputDevice "Mouse1" "CorePointer" InputDevice "Keyboard1" "CoreKeyboard" EndSection