Kali-linux Basic Settings

1.6.1 Start the default service

Kali Linux comes with several network services, which are very useful. However, it is disabled by default. Here, you'll find ways to set up and start each service using various methods.

1. Launch Apache Service

Start the Apache service. The execution commands are as follows:

[email protected]:~# service apache2 start

The output information is as follows:

[ok] Starting web server: apache2.

The output information indicates that the Apache service has been started. To verify that the service is running, you can access the local address in the browser. To access the local address in the browser, the interface shown in 1.59 will be displayed if the server is running.

Figure 1.59 Apache server access interface

2. Start secure Shell (SSH) service

Start the Secure Shell (SSH) service. The execution commands are as follows:

[email protected]:~# service ssh start[ok] Starting OpenBSD Secure Shell server: sshd.

Seeing the above output indicates that the SSH service has been started. To verify that the port of the service is being monitored, execute the command shown below:

[email protected]:~# netstat -tpan | grep 22tcp  0   0 0.0.0.0:22     0.0.0.0:*       LISTEN   7658/sshdtcp6 0   0 :::22           :::*           LISTEN   7658/sshd

3. Start the FTP service

The FTP service is not installed by default, so you need to install the FTP server first. The installation package for the FTP server is not available by default in the software source of the Kali Linux operating system, where a software source needs to be configured. The specific steps to configure the software source are as follows.

(1) Set apt source. Add the following mirror sites to the software source file/etc/apt/sources.list. The execution commands are as follows:

[email protected]:~# vi /etc/apt/sources.listdeb http://mirrors.neusoft.edu.cn/kali/ kali main non-free contribdeb-src http://mirrors.neusoft.edu.cn/kali/ kali main non-free contribdeb http://mirrors.neusoft.edu.cn/kali-security kali/updates main contrib non-free

Once you have added the above sources, you will save the Sources.list file and exit. In this file, the software sources that are added are categorized according to the different repositories. Where Deb refers to the directory of the Deb package; deb-src refers to the source directory. If you do not look at the program or compile, you can not specify DEB-SRC. Since Deb-src and Deb are paired, you can not specify DEB-SRC, but when DEB-SRC is required, Deb must be specified.

(2) After you have added the software source, you need to update the package list before you can use it. To update the package list, execute the command as follows:

[email protected]:~# apt-get update

After the software list is updated, the program is automatically exited.

(3) Install the FTP server. The execution commands are as follows:

[email protected]:~# apt-get install pure-ftpd

Once the FTP server is successfully installed, you can start the service. The execution commands are as follows:

[email protected]:~# service pure-ftpd start

4. Install Chinese Input Method

Kali Linux operating system is not installed by default Chinese input method, the following will introduce the installation of Penguin Chinese input method. The execution commands are as follows:

[email protected]:~# apt-get install fcitx-table-wbpy ttf-wqy-microhei ttf-wqy- zenhei

After executing the above command, the small Penguin Chinese input method was installed successfully. After the installation is successful, you need to start the IME before you can use it. Start the Penguin Chinese input method and execute the command as follows:

[email protected]:~# Fcitx[email protected]:~#[info]/build/buildd-fcitx_4.2.4.1-7-i386-l4w6z_/ fcitx-4.2.4.1/src/lib/fcitx/addon.c:100-load Add-ons profile: Fcitx-table.conf[info]/build/buildd-fcitx_4.2.4.1-7- i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c:100-load Add-ons profile: Fcitx-xim.conf[info]/build/buildd-fcitx_ 4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c:100-load Add-ons profile: Fcitx-lua.conf[info]/build/ buildd-fcitx_4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c:100-load Add-ons profile: Fcitx-pinyin.conf[INFO]/ build/buildd-fcitx_4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c:100-loading Add-ons profile: fcitx-autoeng.conf [INFO]/build/buildd-fcitx_4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c:100-Loading add-on configuration file: Fcitx-xkb.conf[info]/build/buildd-fcitx_4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c:100- Load add-ons profile: Fcitx-ipc.conf[info]/build/buildd-fcitx_4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c : 100-load Add-ons profile: Fcitx-kimpanel-ui.conF[info]/build/buildd-fcitx_4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c:100-Load Add-on configuration file: Fcitx-vk.conf[info]/build/buildd-fcitx_4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c:100- Load add-ons profile: Fcitx-quickphrase.conf[info]/BUILD/BUILDD-FCITX_4.2.4.1-7-I386-L4W6Z_/FCITX-4.2.4.1/SRC/LIB/FCITX/ addon.c:100-load Add-ons profile: Fcitx-remote-module.conf[info]/build/buildd-fcitx_4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/ src/lib/fcitx/addon.c:100-load Add-ons profile: Fcitx-punc.conf[info]/build/buildd-fcitx_4.2.4.1-7-i386-l4w6z_/ fcitx-4.2.4.1/src/lib/fcitx/addon.c:100-load Add-ons profile: Fcitx-dbus.conf[info]/build/buildd-fcitx_4.2.4.1-7- i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c:100-load Add-ons profile: Fcitx-keyboard.conf[info]/build/buildd-fcitx_ 4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c:100-load Add-ons profile: Fcitx-chttrans.conf[info]/build/ buildd-fcitx_4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c:100-loading the Add-in configuration file: Fcitx-fullwidth-char.conf[info]/build/buildd-fcitx_4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c:100-load Add-ons profile: Fcitx-imselector.conf[info]/build/ buildd-fcitx_4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c:100-load Add-ons profile: Fcitx-x11.conf[INFO]/ build/buildd-fcitx_4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c:100-loading the Add-in configuration file: Fcitx-classic-ui.conf[info]/build/buildd-fcitx_4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/lib/fcitx/addon.c:100- Load add-ons profile: Fcitx-xkbdbus.conf[info]/build/buildd-fcitx_4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/im/table/ table.c:155-Loading Code Table file: Wbpy.conf[warn]/build/buildd-fcitx_4.2.4.1-7-i386-l4w6z_/fcitx-4.2.4.1/src/frontend/xim/ xim.c:168-Set Environment Variables Xmodifiers

The output information represents some of the configuration files that the input method loads at startup. The last line prompts you to set the environment variable xmodifiers, and some programs tend to be unusable because the xmodifiers environment variable is set incorrectly. Here's how to set the xmodifiers environment variable (bash, for example):

export XMODIFIERS="@im=YOUR_XIM_NAME"

The your_xim_name in the syntax is the name of the XIM program registered in the system. When the application starts, it increments the variable to find the appropriate Xim server. Therefore, even if several Xim programs are running at the same time in the system, an application can use only one Xim input method at a time.

FCITX the default registered Xim name is FCITX, but if Xmodifiers is set at FCITX startup, FCITX will automatically register the appropriate name with the system settings. If it is not set up, use the following method settings.

You can generally add the following in the ~/.BASHRC file. As shown below:

export XMODIFIERS="@im=fcitx"export XIM=fcitxexport XIM_PROGRAM=fcitx

After adding and saving the above content, re-login to the current user, Fcitx IME will run automatically. If it does not start, execute the following command at the terminal:

[email protected]:~# fcitx

After executing the above command, a keyboard appears in the upper-right corner of the screen to indicate that the IME has been started. The small penguin Input method supports Chinese, pinyin, double spelling and wubi pinyin four kinds of input methods by default, and these input methods use the Ctrl+shift key combination switch by default.

If you want to change the switch between input methods, right-click the keyboard in the upper right corner of the desktop, will pop up 1.60 of the interface shown.

Figure 1.60 FCITX Interface

Selecting the "Configure" command in this interface will display the interface shown in 1.61. Click on the "Global Configuration" tab in this interface and the interface shown in 1.62 will be displayed.

Figure 1.61 FCITX Configuration

Figure 1.62 Global Configuration

From this interface you can see the settings of various shortcut keys, according to their own custom shortcut keys to set up. When you're finished setting up, click the Apply button.

5. Stop the Service

The syntax format for stopping a service is as follows:

service <servicename> stop

<servicename> represents the service that the user wants to stop.

To stop the Apache service, execute the command as follows:

[email protected]:~# service apache2 stop[ ok ] Stopping web server: apache2 … waiting.

From the output information, you can see that the Apache service stopped successfully.

6. Set up service boot up

The syntax format for setting up the service boot starts as follows:

update-rc.d -f <servicename> defaults

<servicename> represents the service that the user wants to boot on.

To set up the SSH service to turn on self-boot:

[email protected]:~# update-rc.d -f ssh defaultsupdate-rc.d: using dependency based boot sequencingupdate-rc.d: warning: default stop runlevel arguments (0 1 6) do not match ssh Default-Stop values (none)insserv: warning: current start runlevel(s) (empty) of script `ssh‘ overrides LSB defaults (2 3 4 5).insserv: warning: current stop runlevel(s) (2 3 4 5) of script `ssh‘ overrides LSB defaults (empty).

As you can see from the output information, the SSH service starts the 2, 3, 4, and 5 runlevel by default. After the system restarts, the SSH service will run automatically.

1.6.2 setting up a wireless network

Wireless networks include both global voice and data networks that allow users to establish long-range wireless connections, as well as infrared and RF technologies optimized for near-range wireless connectivity. This section describes the settings for the WICD network manager, which is used to securely connect to the wireless network. Setting up a wireless network allows users to use Kali Linux wirelessly, doing penetration testing without relying on an Ethernet, so that users can use the computer very freely.

The steps for setting up a wireless network are as follows.

(1) Start the WICD network manager. There are two methods, one is the command line and the other is the graphical interface. On the desktop, select Applications | Internet "| The WICD Network Manager command displays the interface shown in 1.63. If Wicdnetwork Manager is not found on the graphics desktop, the WICD package is not installed in the system. The user can find the WICD package installed on the Add/remove software.

or execute the following command at the terminal:

wicd-gtk --no-tray

After executing the above command, the interface shown in 1.63 will be displayed.

Figure 1.63 WICD network Manager

(2) From this interface you can see all the wireless networks that can be searched, and clearly see the encryption method of each wireless network, the channel used and the intensity of the wireless signal. In this example, select the wireless network Test1 that uses WEP encryption, click the Test1 Properties button, and the interface shown in 1.64 is displayed.

Figure 1.64 Property settings

(3) Select the "Use Encryption" checkbox in this interface, then select the encryption method and enter the password. If you do not want to display the password character, do not tick the check box in front of the password text box. When you're done, click the OK button to return to the figure 1.63 interface. At this point, you can connect to the TEST1 network by clicking the Connect button on the interface.

Kali-linux Basic Settings