mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-10-01 01:25:40 -04:00
layout fixes, indentation and small typo fixes
This commit is contained in:
Jeeppler
parent
02c2621efc
commit
4db5ca5184
@ -18,61 +18,59 @@ The image below shows the default light theme after installation.
|
|||||||
This is the result after applying the steps described here.
|
This is the result after applying the steps described here.
|
||||||
|
|
||||||
|
|
||||||
1 - Change `Workspace Appearance`
|
1. Change `Workspace Appearance`
|
||||||
|
|
||||||
1. Open the `Workspace Appearance` window
|
1. Open the `Workspace Appearance` window
|
||||||
|
|
||||||
Qubes Menu -> System Tools -> System Settings -> Workspace Appearance
|
Qubes Menu -> System Tools -> System Settings -> Workspace Appearance
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
2. Go to `Desktop Theme`
|
2. Go to `Desktop Theme`
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
3. Select `Oxygen` and `Apply` the change
|
3. Select `Oxygen` and `Apply` the change
|
||||||
|
|
||||||
2 - (Optional) Remove blue glowing task items
|
2. (Optional) Remove blue glowing task items
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
1. Adjust Oxygen `Details`
|
1. Adjust Oxygen `Details`
|
||||||
|
|
||||||
Qubes Menu -> System Tools -> System Settings -> Workspace Appearance -> Desktop Theme -> Details (Tab)
|
Qubes Menu -> System Tools -> System Settings -> Workspace Appearance -> Desktop Theme -> Details (Tab)
|
||||||
|
|
||||||
2. Select `Oxygen`
|
2. Select `Oxygen`
|
||||||
|
|
||||||
3. Change `Theme Item -> Task Items` from `Oxygen Task Items` to `Air Task Items`
|
3. Change `Theme Item -> Task Items` from `Oxygen Task Items` to `Air Task Items`
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
4. Apply changes
|
4. Apply changes
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
3 - Change `Application Appearance`
|
3. Change `Application Appearance`
|
||||||
|
|
||||||
1. Open the `Application Appearance` window
|
1. Open the `Application Appearance` window
|
||||||
|
|
||||||
|
Qubes Menu -> System Tools -> System Settings -> Application Appearance
|
||||||
|
|
||||||
Qubes Menu -> System Tools -> System Settings -> Application Appearance
|
2. Go to `Colors`
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
2. Go to `Colors`
|
3. Select `Obsidian Coast`
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
3. Select `Obsidian Coast`
|
4. Apply Changes
|
||||||
|
|
||||||
|
Qubes VM Manager should now look like the image below.
|
||||||
|
|
||||||
4. Apply Changes
|
|
||||||
|
|
||||||
Qubes VM Manager should now look like the image below.
|
**Note:** Chaning the `Window Decorations` from `Plastik for Qubes` will remove the border color and the VM name. The problem with `Plastik for Qubes` is, that it does not overwrite the background and text color for Minimize, Maximize and Close buttons. The three button are therefor hard to read.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
**Note:** Chaning the `Window Decorations` from `Plastik for Qubes` will remove the border color and the VM name. The problem with `Plastik for Qubes` is it does not overwrite the background and text color for Minimize, Maximize and Close buttons. The three button are therefor hard to read.
|
|
||||||
|
|
||||||
Dark XCFE in Dom0
|
Dark XCFE in Dom0
|
||||||
-----------------
|
-----------------
|
||||||
@ -85,27 +83,27 @@ The image below shows the default light theme after installation.
|
|||||||
This is the result after applying the steps described here.
|
This is the result after applying the steps described here.
|
||||||
|
|
||||||
|
|
||||||
1 - Change Appearance
|
1. Change Appearance
|
||||||
|
|
||||||
1. Open the `Appearance` dialog
|
1. Open the `Appearance` dialog
|
||||||
|
|
||||||
Qubes Menu -> System Tools -> Appearance
|
Qubes Menu -> System Tools -> Appearance
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
2. Change Style to `Albatross`
|
2. Change Style to `Albatross`
|
||||||
|
|
||||||
**Note:** The black appearance theme `Xfce-dusk` makes the VM names in the `Qubes OS Manager` unreadable.
|
**Note:** The black appearance theme `Xfce-dusk` makes the VM names in the `Qubes OS Manager` unreadable.
|
||||||
|
|
||||||
2 - *(Optional)* Change Window Manager Style
|
2. *(Optional)* Change Window Manager Style
|
||||||
|
|
||||||
1. Open the `Window Manager` dialog
|
1. Open the `Window Manager` dialog
|
||||||
|
|
||||||
Qubes Menu -> System Tools -> Appearance
|
Qubes Menu -> System Tools -> Appearance
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
2. Change the Theme in the `Style` Tab (e. g. Defcon-IV). All available themes work.
|
2. Change the Theme in the `Style` Tab (e. g. Defcon-IV). All available themes work.
|
||||||
|
|
||||||
|
|
||||||
Dark App VM, Template VM, Standalone VM, HVM (Linux Gnome)
|
Dark App VM, Template VM, Standalone VM, HVM (Linux Gnome)
|
||||||
@ -120,74 +118,74 @@ The advantage of creating a dark themed Template VM is, that each AppVM which is
|
|||||||
|
|
||||||
**Note:** Gnome-Tweak-Tool crashes under Archlinux. A workaround is to assign the AppVM to another TemplateVM (Debian, Fedora) which has Gnome-Tweak-Tool installed. Start the AppVM and configure the settings. Shutdown the machine and switch the template VM back to Archlinux.
|
**Note:** Gnome-Tweak-Tool crashes under Archlinux. A workaround is to assign the AppVM to another TemplateVM (Debian, Fedora) which has Gnome-Tweak-Tool installed. Start the AppVM and configure the settings. Shutdown the machine and switch the template VM back to Archlinux.
|
||||||
|
|
||||||
0 - Start VM
|
1. Start VM
|
||||||
|
|
||||||
**Note:** In case of App VM start the Template on which the AppVM is based on.
|
**Note:** In case of App VM start the Template on which the AppVM is based on.
|
||||||
|
|
||||||
1 - Install `Gnome-Tweak-Tool`
|
2. Install `Gnome-Tweak-Tool`
|
||||||
|
|
||||||
1. Fedora
|
- Fedora
|
||||||
|
|
||||||
sudo dnf install gnome-tweak-tool
|
sudo dnf install gnome-tweak-tool
|
||||||
|
|
||||||
2. Debian
|
- Debian
|
||||||
|
|
||||||
sudo apt-get install gnome-tweak-tool
|
sudo apt-get install gnome-tweak-tool
|
||||||
|
|
||||||
2 - *(Only AppVM)* Stop template and start AppVM
|
3. *(Only AppVM)* Stop template and start AppVM
|
||||||
|
|
||||||
3 - Add `Gnome-Tweak-Tool` to the Application Menu
|
4. Add `Gnome-Tweak-Tool` to the Application Menu
|
||||||
|
|
||||||
1. `Right-click` on VM entry in `Qubes VM Manager` select `Add/remove app shortcuts`
|
1. `Right-click` on VM entry in `Qubes VM Manager` select `Add/remove app shortcuts`
|
||||||
|
|
||||||
2. Select `Tweak Tool` and press the `>` button to add it
|
2. Select `Tweak Tool` and press the `>` button to add it
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
4 - Enable `Global Dark Theme`
|
5. Enable `Global Dark Theme`
|
||||||
|
|
||||||
1. *Debian only*
|
1. *Debian only*
|
||||||
|
|
||||||
cd ~/.config/
|
cd ~/.config/
|
||||||
mkdir gtk-3.0
|
mkdir gtk-3.0
|
||||||
cd gtk-3.0/
|
cd gtk-3.0/
|
||||||
touch settings.ini
|
touch settings.ini
|
||||||
|
|
||||||
2. Start `Tweak Tool` from the VM application menu and set the `Global Dark Theme` switch to `on`
|
2. Start `Tweak Tool` from the VM application menu and set the `Global Dark Theme` switch to `on`
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
5 - *(Optional)* Modify Firefox
|
6. *(Optional)* Modify Firefox
|
||||||
|
|
||||||
**Note:** Firefox uses GTK style settings by default. This can create side effects such as unusable forms or search fields. There are two different ways to avoid this. Either by using a add-on or by overwriting the defaults.
|
**Note:** Firefox uses GTK style settings by default. This can create side effects such as unusable forms or search fields. There are two different ways to avoid this. Either by using a add-on or by overwriting the defaults.
|
||||||
|
|
||||||
- use the theme [GTK+ Dark Theme Global Fixes](https://userstyles.org/styles/111694/gtk-dark-theme-global-fixes) and the [Stylish](https://addons.mozilla.org/en-US/firefox/addon/stylish/) addon
|
- use the theme [GTK+ Dark Theme Global Fixes](https://userstyles.org/styles/111694/gtk-dark-theme-global-fixes) and the [Stylish](https://addons.mozilla.org/en-US/firefox/addon/stylish/) addon
|
||||||
|
|
||||||
- or add the following line to `/rw/config/rc.local`
|
- or add the following line to `/rw/config/rc.local`
|
||||||
|
|
||||||
sed -i.bak "s/Exec=firefox %u/Exec=bash -c 'GTK_THEME=Adwaita:light firefox %u'/g" /usr/share/applications/firefox.desktop
|
sed -i.bak "s/Exec=firefox %u/Exec=bash -c 'GTK_THEME=Adwaita:light firefox %u'/g" /usr/share/applications/firefox.desktop
|
||||||
|
|
||||||
6 - Restart VM or all application
|
7. Restart VM or all application
|
||||||
|
|
||||||
Manually
|
Manually
|
||||||
--------
|
--------
|
||||||
|
|
||||||
Manually works for Debian, Fedora and Archlinux.
|
Manually works for Debian, Fedora and Archlinux.
|
||||||
|
|
||||||
0 - Start VM
|
1. Start VM
|
||||||
|
|
||||||
**Note:** In case of App VM start the Template on which the AppVM is based on.
|
**Note:** In case of App VM start the Template on which the AppVM is based on.
|
||||||
|
|
||||||
1 - Enable `Global Dark Theme`
|
2. Enable `Global Dark Theme`
|
||||||
|
|
||||||
cd ~/.config/
|
cd ~/.config/
|
||||||
mkdir gtk-3.0
|
mkdir gtk-3.0
|
||||||
cd gtk-3.0/
|
cd gtk-3.0/
|
||||||
touch settings.ini
|
touch settings.ini
|
||||||
|
|
||||||
add the following lines to `settings.ini`
|
add the following lines to `settings.ini`
|
||||||
|
|
||||||
[Settings]
|
[Settings]
|
||||||
gtk-application-prefer-dark-theme=1
|
gtk-application-prefer-dark-theme=1
|
||||||
|
|
||||||
2 - follow step 5 and 6 in: Using `Gnome-Tweak-Tool`
|
3. follow step 6 and 7 in: Using `Gnome-Tweak-Tool`
|
||||||
|
|||||||
@ -8,15 +8,15 @@ permalink: /doc/pentesting/
|
|||||||
|
|
||||||
The usage of penetration testing tools outside your own laboratory environment requires the permission of the organization you attack. Penetration testing without such a permission can have legal consequences.
|
The usage of penetration testing tools outside your own laboratory environment requires the permission of the organization you attack. Penetration testing without such a permission can have legal consequences.
|
||||||
|
|
||||||
To avoid such legal conflicts please refer to the [Code of Ethics](https://www.eccouncil.org/Support/code-of-ethics).
|
To avoid such legal conflicts please refer to the [EC-Council: Code of Ethics](https://www.eccouncil.org/Support/code-of-ethics).
|
||||||
|
|
||||||
Penetration Testing
|
Penetration Testing
|
||||||
===================
|
===================
|
||||||
|
|
||||||
"A penetration test, informally pen test, is an attack on a computer system that looks for security weaknesses, potentially gaining access to the computer's features and data." (source [Penetration test](https://en.wikipedia.org/wiki/Penetration_test)).
|
"A penetration test, informally pen test, is an attack on a computer system that looks for security weaknesses, potentially gaining access to the computer's features and data." (source [Penetration test](https://en.wikipedia.org/wiki/Penetration_test)).
|
||||||
|
|
||||||
Penetration Testing Distributions:
|
Penetration Testing Distributions
|
||||||
----------------------------------
|
---------------------------------
|
||||||
|
|
||||||
The following install instructions explain how to setup a penetration testing distribution within Qubes OS.
|
The following install instructions explain how to setup a penetration testing distribution within Qubes OS.
|
||||||
|
|
||||||
@ -27,7 +27,4 @@ The following install instructions explain how to setup a penetration testing di
|
|||||||
Using Qubes OS to host a "hacking" laboratory
|
Using Qubes OS to host a "hacking" laboratory
|
||||||
---------------------------------------------
|
---------------------------------------------
|
||||||
|
|
||||||
Qubes OS is a hypervisor based operating system. Qubes OS can various operating systems such as Linux, Unix or Windows in parallel. Qubes OS can therefor be used to host your own "hacking" laboratory.
|
Qubes OS is a hypervisor based operating system. Qubes OS can host various operating systems such as Linux, Unix or Windows and run them parallel. Qubes OS can therefor be used to host your own "hacking" laboratory.
|
||||||
|
|
||||||
- [Creating and Using HVM Domains](/doc/hvm-create/)
|
|
||||||
- [Templates](/doc/templates/)
|
|
||||||
|
|||||||
@ -23,82 +23,72 @@ How to Create a BlackArch VM
|
|||||||
Create ArchLinux Based BlackArch Template
|
Create ArchLinux Based BlackArch Template
|
||||||
-----------------------------------------
|
-----------------------------------------
|
||||||
|
|
||||||
0 - Create ArchlLinux Template
|
1. Create ArchlLinux Template
|
||||||
|
|
||||||
- Follow the [Archlinux Template instructions](/doc/templates/archlinux/)
|
- Follow the [Archlinux Template instructions](/doc/templates/archlinux/)
|
||||||
|
|
||||||
1 - Update Template
|
|
||||||
|
|
||||||
~~~
|
2. Update Template
|
||||||
sudo pacman -Syyu
|
|
||||||
~~~
|
|
||||||
|
|
||||||
2 - Clone template
|
sudo pacman -Syyu
|
||||||
|
|
||||||
1. Via Qubes VM Manager
|
3. Clone template
|
||||||
|
|
||||||
2. Via command line
|
1. Via Qubes VM Manager
|
||||||
|
|
||||||
~~~
|
2. Via command line
|
||||||
qvm-clone archlinux blackarch
|
|
||||||
~~~
|
|
||||||
|
|
||||||
3 - Install BlackArch repository
|
qvm-clone archlinux blackarch
|
||||||
|
|
||||||
~~~
|
4. Install BlackArch repository
|
||||||
$ curl -O https://blackarch.org/strap.sh
|
|
||||||
|
|
||||||
# The SHA1 sum should match: 86eb4efb68918dbfdd1e22862a48fda20a8145ff
|
$ curl -O https://blackarch.org/strap.sh
|
||||||
$ sha1sum strap.sh
|
|
||||||
|
|
||||||
# Set execute bit
|
# The SHA1 sum should match: 86eb4efb68918dbfdd1e22862a48fda20a8145ff
|
||||||
$ chmod +x strap.sh
|
$ sha1sum strap.sh
|
||||||
|
|
||||||
# Run strap.sh
|
# Set execute bit
|
||||||
$ sudo ./strap.sh
|
$ chmod +x strap.sh
|
||||||
~~~
|
|
||||||
|
|
||||||
4 - Install tools
|
# Run strap.sh
|
||||||
|
$ sudo ./strap.sh
|
||||||
|
|
||||||
- install all tools
|
5. Install tools
|
||||||
|
|
||||||
~~~
|
- install all tools
|
||||||
sudo pacman -S blackarch
|
|
||||||
~~~
|
|
||||||
|
|
||||||
- or by category:
|
sudo pacman -S blackarch
|
||||||
|
|
||||||
~~~
|
- or by category:
|
||||||
# list available categories
|
|
||||||
pacman -Sg | grep blackarch
|
|
||||||
|
|
||||||
# install category
|
# list available categories
|
||||||
sudo pacman -S blackarch-<category>
|
pacman -Sg | grep blackarch
|
||||||
|
|
||||||
# example
|
# install category
|
||||||
sudo pacman -S blackarch-forensic
|
sudo pacman -S blackarch-<category>
|
||||||
~~~
|
|
||||||
|
|
||||||
- or specific tool
|
# example
|
||||||
|
sudo pacman -S blackarch-forensic
|
||||||
|
|
||||||
~~~
|
- or specific tool
|
||||||
# Search for tool
|
|
||||||
pacman -Ss <tool-name>
|
|
||||||
|
|
||||||
# Install tool
|
# Search for tool
|
||||||
sudo pacman -S <tool-name>
|
pacman -Ss <tool-name>
|
||||||
|
|
||||||
# Example
|
# Install tool
|
||||||
pacman -Ss burpsuite
|
sudo pacman -S <tool-name>
|
||||||
sudo pacman -S burpsuite
|
|
||||||
~~~
|
|
||||||
|
|
||||||
5 - Create a AppVMs based on the `ptf` template
|
# Example
|
||||||
|
pacman -Ss burpsuite
|
||||||
|
sudo pacman -S burpsuite
|
||||||
|
|
||||||
- (Optional) Attach necessary devices
|
6. Create a AppVMs based on the `ptf` template
|
||||||
|
|
||||||
|
- (Optional) Attach necessary devices
|
||||||
|
|
||||||
Alternative Options to BlackArch
|
Alternative Options to BlackArch
|
||||||
--------------------------------
|
--------------------------------
|
||||||
|
|
||||||
- [Kali](/doc/kali/)
|
- [Kali](/doc/kali/)
|
||||||
- [PenTester Framework (PTF)](/doc/ptf/)
|
- [PenTester Framework (PTF)](/doc/ptf/)
|
||||||
|
- [Pentesting](/doc/pentesting/)
|
||||||
|
|||||||
@ -24,213 +24,172 @@ There are multiple ways to create a Kali Linux VM. One way is to create a HVM an
|
|||||||
Kali Linux HVM
|
Kali Linux HVM
|
||||||
--------------
|
--------------
|
||||||
|
|
||||||
0 - Download the Kali installation DVD
|
1. Download the Kali installation DVD
|
||||||
|
|
||||||
1 - Create a new HVM
|
2. Create a new HVM
|
||||||
|
|
||||||
2 - Start the HVM with attached CD/DVD
|
3. Start the HVM with attached CD/DVD
|
||||||
|
|
||||||
~~~
|
qvm-start <hvm-name> --cdrom <vm-name>:/home/user/Downloads/<iso-name>.iso
|
||||||
qvm-start <hvm-name> --cdrom <vm-name>:/home/user/Downloads/<iso-name>.iso
|
|
||||||
~~~
|
|
||||||
|
|
||||||
Create Debian Based Kali Template
|
Create Debian Based Kali Template
|
||||||
---------------------------------
|
---------------------------------
|
||||||
|
|
||||||
0 - (Optional) Install `debian-8` template (if not already installed)
|
1. *(Optional)* Install `debian-8` template (if not already installed)
|
||||||
|
|
||||||
1 - Update your `debian-8` template
|
2. Update your `debian-8` template
|
||||||
|
|
||||||
~~~
|
sudo apt-get update
|
||||||
sudo apt-get update
|
sudo apt-get dist-upgrade
|
||||||
sudo apt-get dist-upgrade
|
|
||||||
~~~
|
|
||||||
|
|
||||||
2 - Clone `debian-8` template (two options)
|
3. Clone `debian-8` template (two options)
|
||||||
|
|
||||||
1. Via Qubes VM Manager
|
1. Via Qubes VM Manager
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
2. Via command line
|
2. Via command line
|
||||||
|
|
||||||
~~~
|
qvm-clone debian-8 kali
|
||||||
qvm-clone debian-8 kali
|
|
||||||
~~~
|
|
||||||
|
|
||||||
3 - Start and upgrade the `kali` Template from Debian 8 to Debian 9
|
4. Start and upgrade the `kali` Template from Debian 8 to Debian 9
|
||||||
|
|
||||||
~~~
|
sudo sed -i 's/jessie/stretch/g' /etc/apt/sources.list
|
||||||
user@kali:~$ sudo sed -i 's/jessie/stretch/g' /etc/apt/sources.list
|
sudo sed -i 's/jessie/stretch/g' /etc/apt/sources.list.d/qubes-r3.list
|
||||||
user@kali:~$ sudo sed -i 's/jessie/stretch/g' /etc/apt/sources.list.d/qubes-r3.list
|
sudo apt-get update
|
||||||
user@kali:~$ sudo apt-get update
|
sudo apt-get dist-upgrade
|
||||||
user@kali:~$ sudo apt-get dist-upgrade
|
sudo apt-get autoremove
|
||||||
user@kali:~$ sudo apt-get autoremove
|
|
||||||
~~~
|
|
||||||
|
|
||||||
NOTICE: From now on there are two possible ways either doing everything manually or automatically with [Katoolin](https://github.com/LionSec/katoolin).
|
**Note:** From now on there are two possible ways either doing everything manually or automatically with [Katoolin](https://github.com/LionSec/katoolin).
|
||||||
|
|
||||||
Katoolin is a script (written in Python) which helps you to install Kali tools.
|
Katoolin is a script (written in Python) which helps you to install Kali tools.
|
||||||
|
|
||||||
4 *manually* - Add Kali Linux repositories
|
5. *manually* - Add Kali Linux repositories
|
||||||
|
|
||||||
1. Add Kali Linux repositories to `/etc/apt/sources.list`
|
1. Add Kali Linux repositories to `/etc/apt/sources.list`
|
||||||
|
|
||||||
~~~
|
deb http://http.kali.org/kali kali-rolling main contrib non-free
|
||||||
deb http://http.kali.org/kali kali-rolling main contrib non-free
|
deb http://repo.kali.org/kali kali-bleeding-edge main
|
||||||
deb http://repo.kali.org/kali kali-bleeding-edge main
|
|
||||||
~~~
|
|
||||||
|
|
||||||
2. Add kali signing key
|
2. Add kali signing key
|
||||||
|
|
||||||
- The signing key can be found here [Download Kali Linux Images Securely](https://www.kali.org/downloads/)
|
- The signing key can be found here [Download Kali Linux Images Securely](https://www.kali.org/downloads/)
|
||||||
|
|
||||||
~~~
|
sudo apt-key adv --keyserver hkp://keys.gnupg.net --recv-keys 7D8D0BF6
|
||||||
sudo apt-key adv --keyserver hkp://keys.gnupg.net --recv-keys 7D8D0BF6
|
sudo apt-get update
|
||||||
sudo apt-get update
|
|
||||||
~~~
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
4 *katoolin* - Install Katoolin and add Kali Linux repositories
|
6. *katoolin* - Install Katoolin and add Kali Linux repositories
|
||||||
|
|
||||||
1. Install Katoolin
|
1. Install Katoolin
|
||||||
|
|
||||||
~~~
|
sudo apt-get install git
|
||||||
sudo apt-get install git
|
git clone https://github.com/LionSec/katoolin.git
|
||||||
git clone https://github.com/LionSec/katoolin.git
|
sudo cp katoolin/katoolin.py /usr/bin/katoolin
|
||||||
sudo cp katoolin/katoolin.py /usr/bin/katoolin
|
sudo chmod +x /usr/bin/katoolin
|
||||||
sudo chmod +x /usr/bin/katoolin
|
rm -rf katoolin
|
||||||
rm -rf katoolin
|
|
||||||
~~~
|
|
||||||
|
|
||||||
2. Add Kali Linux repositories
|
2. Add Kali Linux repositories
|
||||||
|
|
||||||
- start katoolin
|
- start katoolin
|
||||||
|
|
||||||
~~~
|
sudo katoolin
|
||||||
sudo katoolin
|
|
||||||
~~~
|
|
||||||
|
|
||||||
- select 'Add Kali repositories & Update'
|
- select 'Add Kali repositories & Update'
|
||||||
|
|
||||||
~~~
|
1) Add Kali repositories & Update
|
||||||
1) Add Kali repositories & Update
|
2) View Categories
|
||||||
2) View Categories
|
3) Install classicmenu indicator
|
||||||
3) Install classicmenu indicator
|
4) Install Kali menu
|
||||||
4) Install Kali menu
|
5) Help
|
||||||
5) Help
|
|
||||||
|
|
||||||
kat > 1
|
kat > 1
|
||||||
~~~
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
- select 'Add kali linux repositories'
|
- select 'Add kali linux repositories'
|
||||||
|
|
||||||
~~~
|
1) Add kali linux repositories
|
||||||
1) Add kali linux repositories
|
2) Update
|
||||||
2) Update
|
3) Remove all kali linux repositories
|
||||||
3) Remove all kali linux repositories
|
4) View the contents of sources.list file
|
||||||
4) View the contents of sources.list file
|
|
||||||
|
|
||||||
What do you want to do ?> 1
|
What do you want to do ?> 1
|
||||||
~~~
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
- update Kali repositories
|
- update Kali repositories
|
||||||
|
|
||||||
~~~
|
|
||||||
1) Add kali linux repositories
|
|
||||||
2) Update
|
|
||||||
3) Remove all kali linux repositories
|
|
||||||
4) View the contents of sources.list file
|
|
||||||
|
|
||||||
What do you want to do ?> 2
|
1) Add kali linux repositories
|
||||||
~~~
|
2) Update
|
||||||
|
3) Remove all kali linux repositories
|
||||||
|
4) View the contents of sources.list file
|
||||||
|
|
||||||
- quit katoolin by pressing `CRTL` + `c` keys
|
What do you want to do ?> 2
|
||||||
|
|
||||||
~~~
|
- quit katoolin by pressing `CRTL` + `c` keys
|
||||||
What do you want to do ?> ^CShutdown requested...Goodbye...
|
|
||||||
~~~
|
|
||||||
|
|
||||||
5 - Cleanup and update `kali` template
|
What do you want to do ?> ^CShutdown requested...Goodbye...
|
||||||
|
|
||||||
~~~
|
7. Cleanup and update `kali` template
|
||||||
sudo apt-get dist-upgrade
|
|
||||||
sudo apt-get autoremove
|
|
||||||
~~~
|
|
||||||
|
|
||||||
|
sudo apt-get dist-upgrade
|
||||||
|
sudo apt-get autoremove
|
||||||
|
|
||||||
6 - Shutdown and trim `kali` template
|
8. Shutdown and trim `kali` template
|
||||||
|
|
||||||
- Shutdown `kali` template
|
- Shutdown `kali` template
|
||||||
|
|
||||||
~~~
|
sudo shutdown -h now
|
||||||
sudo shutdown -h now
|
|
||||||
~~~
|
|
||||||
|
|
||||||
- In `dom0` console:
|
- In `dom0` console:
|
||||||
|
|
||||||
~~~
|
qvm-trim-template kali
|
||||||
qvm-trim-template kali
|
|
||||||
~~~
|
|
||||||
|
|
||||||
7 - Start image
|
9. Start image
|
||||||
|
|
||||||
8 *manually* - Install tools
|
10. *manually* - Install tools
|
||||||
|
|
||||||
**Warning:** `kali-linux` and `kali-linux-full` does currently not work properly. Please use `Katoolin` or `PTF`.
|
**Warning:** `kali-linux` and `kali-linux-full` does currently not work properly. Please use `Katoolin` or `PTF`.
|
||||||
|
|
||||||
1. List available packages
|
1. List available packages
|
||||||
|
|
||||||
~~~
|
sudo apt-cache search kali-linux
|
||||||
sudo apt-cache search kali-linux
|
|
||||||
~~~
|
|
||||||
|
|
||||||
2. Select and install tools
|
2. Select and install tools
|
||||||
|
|
||||||
- install base system
|
- install base system
|
||||||
|
|
||||||
~~~
|
sudo apt-get install kali-linux
|
||||||
sudo apt-get install kali-linux
|
|
||||||
~~~
|
|
||||||
|
|
||||||
- or install all tools
|
- or install all tools
|
||||||
|
|
||||||
~~~
|
sudo apt-get install kali-linux-full
|
||||||
sudo apt-get install kali-linux-full
|
|
||||||
~~~
|
|
||||||
|
|
||||||
- or select specific (example):
|
- or select specific (example):
|
||||||
|
|
||||||
~~~
|
sudo apt-get install kali-linux-top10 kali-linux-web
|
||||||
sudo apt-get install kali-linux-top10 kali-linux-web
|
11. *katoolin* - Install tools
|
||||||
~~~
|
|
||||||
|
|
||||||
8 *katoolin* - Install tools
|
1. View Categories
|
||||||
|
|
||||||
1. View Categories
|
- start katoolin
|
||||||
|
|
||||||
- start katoolin
|
sudo katoolin
|
||||||
|
|
||||||
~~~
|
- select `2) View Categories`
|
||||||
sudo katoolin
|
|
||||||
~~~
|
|
||||||
|
|
||||||
- select `2) View Categories`
|
2. Select the categories/tools you want to install
|
||||||
|
|
||||||
2. Select the categories/tools you want to install
|
- For more information on how to use Katoolin see [How to Auto Install All Kali Linux Tools Using “Katoolin” on Debian/Ubuntu](http://www.tecmint.com/install-kali-linux-tools-using-katoolin-on-ubuntu-debian/)
|
||||||
|
|
||||||
- For more information on how to use Katoolin see [How to Auto Install All Kali Linux Tools Using “Katoolin” on Debian/Ubuntu](http://www.tecmint.com/install-kali-linux-tools-using-katoolin-on-ubuntu-debian/)
|
- **Note:** The `all` option does not work for `Information Gathering`, `Web Apps`, `Forensic Tools`, `Reverse Engineering` and `Extra`.
|
||||||
|
|
||||||
- **Note:** The `all` option does not work for `Information Gathering`, `Web Apps`, `Forensic Tools`, `Reverse Engineering` and `Extra`.
|
12. Create a AppVMs based on the `kali` template
|
||||||
|
|
||||||
9 - Create a AppVMs based on the `kali` template
|
- (Optional) Attach necessary devices
|
||||||
|
|
||||||
- (Optional) Attach necessary devices
|
|
||||||
|
|
||||||
|
|
||||||
Alternative Options to Kali
|
Alternative Options to Kali
|
||||||
@ -238,3 +197,4 @@ Alternative Options to Kali
|
|||||||
|
|
||||||
- [BlackArch](/doc/blackarch/)
|
- [BlackArch](/doc/blackarch/)
|
||||||
- [PenTester Framework (PTF)](/doc/ptf/)
|
- [PenTester Framework (PTF)](/doc/ptf/)
|
||||||
|
- [Pentesting](/doc/pentesting/)
|
||||||
|
|||||||
@ -24,114 +24,91 @@ PTF attempts to install all of your penetration testing tools (latest and greate
|
|||||||
Create Debian Based Penetration Testers Framework (PTF) Template
|
Create Debian Based Penetration Testers Framework (PTF) Template
|
||||||
----------------------------------------------------------------
|
----------------------------------------------------------------
|
||||||
|
|
||||||
1 - Create PTF template
|
1. Create PTF template
|
||||||
|
|
||||||
1. Follow the [Create Debian Based Kali Template](/doc/kali/) till step 7.
|
1. Follow [Create Debian Based Kali Template](/doc/kali/) till step 7.
|
||||||
2. (Optional) Rename the cloned template to `ptf`
|
|
||||||
|
|
||||||
2 - Download PTF
|
2. (Optional) Rename the cloned template to `ptf`
|
||||||
|
|
||||||
~~~
|
2. Download PTF
|
||||||
sudo apt-get install git
|
|
||||||
cd /opt
|
|
||||||
sudo git clone https://github.com/trustedsec/ptf.git
|
|
||||||
~~~
|
|
||||||
|
|
||||||
- (Optional) Configure PTF
|
sudo apt-get install git
|
||||||
|
cd /opt
|
||||||
|
sudo git clone https://github.com/trustedsec/ptf.git
|
||||||
|
|
||||||
1. Go to configuration directory
|
- (Optional) Configure PTF
|
||||||
|
|
||||||
~~~
|
1. Go to configuration directory
|
||||||
cd /opt/ptf/config
|
|
||||||
~~~
|
|
||||||
|
|
||||||
2. Edit the configuration file
|
cd /opt/ptf/config
|
||||||
|
|
||||||
for example by using vim:
|
2. Edit the configuration file
|
||||||
|
|
||||||
~~~
|
for example by using vim:
|
||||||
sudo vim ptf.config
|
|
||||||
~~~
|
|
||||||
|
|
||||||
The configuration options are described in the `ptf.config` file
|
sudo vim ptf.config
|
||||||
|
|
||||||
4 - Install PTF
|
the configuration options are described in the `ptf.config` file
|
||||||
|
|
||||||
~~~
|
3. Install PTF
|
||||||
cd /opt/ptf
|
|
||||||
sudo ./ptf
|
|
||||||
~~~
|
|
||||||
|
|
||||||
**Note:** the config file has to be in the same directory as the executable. It is not
|
cd /opt/ptf
|
||||||
|
sudo ./ptf
|
||||||
|
|
||||||
|
**Note:** the config file has to be in the same directory as the executable. It is not
|
||||||
possible to do sudo ptf/ptf
|
possible to do sudo ptf/ptf
|
||||||
|
|
||||||
PTF will put itself into `/usr/local/bin/ptf`. You can use `ptf` from now on.
|
PTF will put itself into `/usr/local/bin/ptf`. You can use `ptf` from now on.
|
||||||
|
|
||||||
5 - Install/Update modules (tools)
|
4. Install/Update modules (tools)
|
||||||
|
|
||||||
1. Start PTF
|
1. Start PTF
|
||||||
|
|
||||||
~~~
|
sudo ptf
|
||||||
sudo ptf
|
|
||||||
~~~
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
2. Show available modules (tools)
|
2. Show available modules (tools)
|
||||||
|
|
||||||
~~~
|
ptf> show modules
|
||||||
ptf> show modules
|
|
||||||
~~~
|
|
||||||
|
|
||||||
3. Install/Update modules (all/)
|
3. Install/Update modules (all/)
|
||||||
|
|
||||||
- Install/Update all tools
|
- Install/Update all tools
|
||||||
|
|
||||||
~~~
|
ptf> use modules/install_update_all
|
||||||
ptf> use modules/install_update_all
|
|
||||||
~~~
|
|
||||||
|
|
||||||
- or by category Install/Update
|
- or by category Install/Update
|
||||||
|
|
||||||
~~~
|
ptf> use modules/code-audit/install_update_all
|
||||||
ptf> use modules/code-audit/install_update_all
|
|
||||||
~~~
|
|
||||||
|
|
||||||
- or individually (example Metasploit)
|
- or individually (example Metasploit)
|
||||||
|
|
||||||
1. Search for module
|
1. Search for module
|
||||||
|
|
||||||
~~~
|
ptf> search metasploit
|
||||||
ptf> search metasploit
|
[*] Search results below:
|
||||||
[*] Search results below:
|
modules/exploitation/metasploit
|
||||||
modules/exploitation/metasploit
|
|
||||||
~~~
|
|
||||||
|
|
||||||
2. Use module
|
2. Use module
|
||||||
|
|
||||||
~~~
|
ptf> use modules/exploitation/metasploit
|
||||||
ptf> use modules/exploitation/metasploit
|
ptf:(modules/exploitation/metasploit)>
|
||||||
ptf:(modules/exploitation/metasploit)>
|
|
||||||
~~~
|
|
||||||
|
|
||||||
3. Install module
|
3. Install module
|
||||||
|
|
||||||
~~~
|
ptf:(modules/exploitation/metasploit)>install
|
||||||
ptf:(modules/exploitation/metasploit)>install
|
|
||||||
~~~
|
|
||||||
|
|
||||||
4. Run Metasploit
|
4. Run Metasploit
|
||||||
|
|
||||||
~~~
|
ptf:(modules/exploitation/metasploit)>exit
|
||||||
ptf:(modules/exploitation/metasploit)>exit
|
ptf> quit
|
||||||
ptf> quit
|
[*] Exiting PTF - the easy pentest platform creation framework.
|
||||||
[*] Exiting PTF - the easy pentest platform creation framework.
|
sudo msfconsole
|
||||||
~$ sudo msfconsole
|
|
||||||
~~~
|
|
||||||
|
|
||||||
6 - Create a AppVMs based on the `ptf` template
|
5. Create a AppVMs based on the `ptf` template
|
||||||
|
|
||||||
- (Optional) Attach necessary devices
|
- (Optional) Attach necessary devices
|
||||||
|
|
||||||
|
|
||||||
Alternative Options to PTF
|
Alternative Options to PTF
|
||||||
@ -139,3 +116,4 @@ Alternative Options to PTF
|
|||||||
|
|
||||||
- [BlackArch](/doc/blackarch/)
|
- [BlackArch](/doc/blackarch/)
|
||||||
- [Kali](/doc/kali/)
|
- [Kali](/doc/kali/)
|
||||||
|
- [Pentesting](/doc/pentesting/)
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user