SETUP

PRIMARY CATEGORY → PENTESTING

Environment Customization

Component	Role
Parrot	Operative System	See more
bspwm	Windows Manager	See more
sxhkd	Hotkey Daemon	See more
Polybar	Status Bar	See more
Picom	Windows Visualizer (Compositor)	See more
Rofi	Application Launcher	See more
Feh	Image Viewer (Desktop Wallpaper)	See more
Kitty	Terminal Emulator	See more
ZSH	Shell	See more
Neovim	Text Editor	See more

Components ⟡

• 
  • ZSH
• 
  • BSPWM
• 
  • SXHKD
• 
  • POLYBAR
• 
  • PICOM
• 
  • ROFI
• 
  • FEH
• 
  • KITTY
• 
  • NEOVIM

Miscellaneous Δ

• 
  • BAT
• 
  • LSD
• 
  • FZF

Information 🛈

This Custom Linux Environment is deployed in Parrot OS 🦜

Configuration Files

Reference

All necessary Configuration Files can be found in the above link or in the Components Documentation

Configuration Files Structure

.
├── bspwm
│   ├── bin
│   │   └── bspwm_resize.sh
│   ├── bspwmrc
│   └── src
│       └── bspwmrc.sh
├── kitty
│   ├── color.ini
│   └── kitty.conf
├── picom
│   └── picom.conf
├── polybar
│   ├── bin
│   │   ├── launch.sh
│   │   └── modules
│   │       ├── ethernet_status.sh
│   │       ├── target_to_hack.sh
│   │       └── vpn_status.sh
│   ├── current.ini
│   └── workspace.ini
├── README.md
├── sxhkd
│   └── sxhkdrc
└── zsh
    ├── plugins
    │   └── zsh-syntaxhighlighting
    │       └── themes
    │           └── dracula.zsh
    ├── src
    │   └── custom.zsh
    ├── themes
    │   └── p10k
    │       ├── root
    │       │   └── .p10k.zsh
    │       └── users
    │           └── .p10k.zsh
    └── .zshrc

Deployment Flow

The Deployment Flow would be →

EXCALIDRAW BANNER

Previous Steps

Before start with the above Components’ Installation and Configuration →

$ sudo apt update # Repositories' update

$ sudo parrot-upgrade

CAUTION

Be aware that the following upgrading way is not recommended →

$ sudo apt upgrade # Or sudo apt full-upgrade

The above way may arises several errors such as the Kernel Panic ones on reboot due to specific packages

Therefore, the Parrot Team has created parrot-upgrade, a simple bash script, to avoid the mentioned problems

$ command -V parrot-upgrade
parrot-upgrade is /usr/bin/parrot-upgrade

#!/bin/bash
set -e
DEBIAN_FRONTEND="noninteractive"
DEBIAN_PRIORITY="critical"
DEBCONF_NOWARNINGS="yes"
export DEBIAN_FRONTEND DEBIAN_PRIORITY DEBCONF_NOWARNINGS
apt update || echo failed to update index lists
dpkg --configure -a || echo failed to fix interrupted upgrades
apt --fix-broken --fix-missing install || echo failed to fix conflicts
apt -y --fix-broken --fix-missing full-upgrade
apt -y full-upgrade

Thus, on Parrot OS, instead of this →

$ sudo apt update && sudo apt upgrade -y # Wrong!

Do this →

$ sudo apt update && sudo parrot-upgrade

Environment Dependencies →

$ sudo apt install -y -- zenity build-essential git vim xcb libxcb-util0-dev libxcb-ewmh-dev libxcb-randr0-dev libxcb-icccm4-dev libxcb-keysyms1-dev libxcb-xinerama0-dev libasound2-dev libxcb-xtest0-dev libxcb-shape0-dev

Additional Packages →

$ sudo apt install -y -- scrot scrub xclip bar locate ranger neofetch wmname acpi imagemagick cmatrix

---

Additional Notes

Sessions Management and Shutdown

During the installation of the above components, the user will have to be shutting down, restarting, logging out or simply blocking (i.e lock) the current session

This actions can be performed as follows →

Shut Down

$ sudo poweroff

Restart

$ sudo reboot

Log out

$ loginctl list-sessions # Get the Session's Number
$ loginctl terminate-session <session_number> # Finish a Session

INFO

If the above command is not available because of the system has not been initialized with systemd, use the following one →

$ pkill -SIGTERM --euid "$( id -u )" # Or pkill -15

This allows to all the processes related to the EUID to terminate corrrectly and clean up resources

If any process does not respond to the SIGTERM signal, just sent a KILL signal to it

$ pkill -KILL --euid "$( id -u )" # Or pkill -9

Note that all signal types and their associated numbers can be enumerated as follows through these shell builtins →

$ kill -l # Or trap -l

Session Lock

It can be handled through the X Session Manager called lightDM

To interact with the lightdm daemon, the dm-tool binary comes into actions

$ dm-tool switch-to-greeter # Like the Change-User option in Windows

$ dm-tool lock # Like Windows + L in Windows

INFO

If lightdm does not manages the user sessions and the host has been booted with systemd (i.e. PID 1), then try this →

$ loginctl list-sessions
$ loginctl lock-session SESSION_NUMBER