I Love the New Windows Terminal

I’ll just say it, I love the new Windows Terminal. This thing is great. It appears the finally took some lessons from the open source community, specifically tiling window managers like my beloved I3. It has tabs, panes, configurable color schemes, transparency, hardware accelerated graphics, can launch shells for cmd, posh, and azure all right there.

Screenshot of Windows TerminalI installed it yesterday after finding out that it’s reached version 1.0. We have the Windows store blocked on corporate devices, so I had to download the package and do an offline installation with Add-AppxPackage. Install was quick and easy.

The panes are an amazing improvement.  It’s something I’d gotten VERY used to from having customized i3 installed on my Kali boxes and I always missed it when I had to switch back to Windows.  So it’s nice to be able to just spawn new panes and switch around with keyboard shortcuts.

I haven’t dug too deeply into the settings config file yet. But it looks easy enough and includes links for more info. I absolutely plan to rice this thing as heavily as I do my Kali installs.  But for now I’m just happy to have this thing available.

I’ll often use multiple terminals to do things like keep multiple ping loops. Generally while making routing/switching changes etc. I’ll have one loop per site. I’ve always hated arranging the windows manually. I also often use multiple windows when stacking ps remote sessions. So that will also be nice to just pop a pane and let it go. You can set custom environment variables for each platform as well. So I can set specific variables for POSH and CLI. that will be quite handy as well.

So there you have it, and I’ll say it one more time. I love the new Windows Terminal. Kudos to the team who built it.

Ricing Kali Linux – Part 3

Forward

If you haven’t gone through parts one and two, you should definitely do so before proceeding.  In this tutorial we will cover installing the rofi application launcher, installing the polybar toolbar, and doing some additional tweaking to the UI elements.

Installing Rofi
The Rofi Application Launcher

This is fairly simple. Running “apt install rofi” will get the program installed. Then you just need to edit your ~/.i3/config file. Look for the line “bindsym Mod1+d exec dmenu_run” and replace it with “bindsym Mod1+d exec rofi -show run”. Log out, back in, test it and it and if it works… SNAP THE VM.

Install Polybar

Start by installing the pre-requisistes. Run the command “apt install cmake cmake-data libcairo2-dev libxcb1-dev libxcb-ewmh-dev libxcb-icccm4-dev libxcb-image0-dev libxcb-randr0-dev libxcb-util0-dev libxcb-xkb-dev pkg-config python-xcbgen xcb-proto libxcb-xrm-dev libasound2-dev libmpdclient-dev libiw-dev libcurl4-openssl-dev libpulse-dev mpd libxcb-composite0-dev”

Once that is done, download polybar  by running “git clone https://github.com/jaagr/polybar.git”, the build it by running “cd polybar && ./build.sh” You will be prompted to determine what you want to install, I just say yes to everything YMMV. Do your homework on that.

To actually turn on polybar, comment out the following section:
bar {
status_command i3status -t
}
Add the following line (possibly adjusting for your system:
exec_always –no-startup-id polybar pyrrh1c &

Once polybar is installed, you will need to configure it. I could write a lengthy tutorial on that… But for the sake of brevity you can just download my polybar config file and look at how it’s set up.  This is the one piece I couldn’t reduce to an easy walk through. Basically, just make a folder in your .config folder called polybar, then copy the config file into it.

Install some additional Fonts

Polybar uses some special unicode characters. This doesn’t work well unless you install the appropriate fonts. (mainly siji and unifont) You can install unifont by simply running “apt install unifont”. Install Siji by running the following commands:
git clone https://github.com/stark/siji.git
cd siji
./install.sh
Once that’s done, add the following lines to your .bashrc file
xset +fp /root/.fonts
xset fp rehash

Install Compton
PolyBar and Compton

Compton is a desktop compositor. It basically helps glue things together. To get it running, rust run “apt install compton”, then when it’s done edit your ~/.i3/config file an add the line “exec compton”.At this point your box should look somewhat like the one to the left.

Configure the Exit Sequence to Actually Exit

Edit your ~/.i3/config file. Look for the line “bindsym Mod1+Shift+e exec “i3-nagbar -t warning -m ‘You pressed the exit shortcut. Do you really want to exit i3? this will end you X session.” Change it to “bindsym Mod1+Shift+e exec i3-msg exit”. You will no longer be nagged when you want to exit.:q

That’s all for now. Stay tuned as I may do a more thorough overview for PolyBar at some point. Thanks for reading!

Ricing Kali Linux – Part 1

Forward

In this tutorial I’m going to show you the basic techniques I use when ricing Kali Linux. But in case you don’t already know, let’s explain what ricing is first. Urban Dictionary defines ricing like this: “Ricing: To rice, or to soup up a crappy car with the  mistaken idea that type ‘R’ stickers and performance yellow paint make it go faster.” In the spirit of that, the tweaks explained here don’t technically make Kali a more effective offensive security platform in and of themselves, but I find they make the interface easier to use, hence they boost my productivity. Let’s be honest, who doesn’t like a customized environment?

Before we start, you may want to check out /r/unixart or /r/unixporn for some inspiration.

Download Kali

You can obtain the latest builds (ISO Images, OVA templates, etc.) from the Kali Linux download page or from the Offensive Security downloads page. For this tutorial, I’m going to deploy Kali virtually using VirtualBox. For the remainder of the tutorial, I’ll assume you are doing the same thing.  You can obtain VirtualBox that from their download page

Install/Deploy Kali

Since we’re using VirtualBox, I downloaded and imported the 2018.4 OVA template from Offensive Security. If you need help doing that, take a look at the  documentation. I named my machine “Pyrrh1c Linux” to differentiate it later from a stock Kali VM.

Immediately after you import the OVA, take a snapshot of the VM. I usually name it something like “VM Imported”.  This allows me to undo any changes since the last snapshot was taken, which is important because mistakes happen, and it’s nice to only have to do one step over again instead of numerous.

Power on the machine, and you will shortly be at the login screen. No Install required! If you are following along and doing a traditional install of Kali and need some pointers for the install process, you may want to take a look a the Kali Linux Official Documentation.

Initial OS Preparations

Open up a terminal window and run the commands “apt update”, then “apt upgrade”. This ensures you have all the latest packages on your install. Go pour out a glass of Kraken, this will take a minute…  When you get to the step that asks about grub, use the space bar to select /dev/sda and hit OK.   

Ready to Go

With the OS installed and updated we are ready to get started customizing. Part 2 will covering installing the i3 window manager, feh, wal and rofi. That’s all for now!

Installing Kali on a Raspberry Pi Zero W

Overview

I love my little Pi Zero W’s, and I love Kali. So why not combine the two? So here’s a post about  Installing Kali Linux on a Raspberry Pi Zero W.   I’ve done this before, and it’s reasonably well documented elsewhere, but I hate googling for all the pieces each time I do this so I figured I’d make a blog post documenting it all for the future so I’ve got all the links in one place

FWIW, I do most of my daily driving on Windows because that’s what I use at work. Hence this will be written for a Windows PC. It’s also high level because honestly, this is easy and if you’re goal is to install Kali on an rpi0w, you probably don’t need much hand holding. 😉

Materials Needed
Process
  1. Format the card with the flasher utility
  2. Write the ISO to the card with Etcher.
  3. Boot up the pi.
References

A Little Housekeeping

Been upgrading the hosts to ESXi 6.5. (Or at least the ones that can be upgraded.  What a dream! I haven’t used it yet but I can’t wait to deploy this at $job.  Such an improvement over 5.5/6.0.  The new web interface actually works.

Haven’t got much done on the infosec front lately. Boo. Life has been getting in the way, as happens.  At any rate, looking forward to getting these hosts finished and moving on.

Additionally, I recently learned about another sweet item called LibreNMS.  Will be rolling that out onto the Pyrrhic network as well.

The Screen Command

So there are times where I only have a single SSH session but want to be able to monitor multiple running processes. For example, metasploit, beef, and bettercap work well together, but it’s nice to be able to concurrently watch the output of all of them.

So I discovered the screen command. It let’s me split up a single session into multiple smaller sessions.  While it seems really powerful, thus far I’m just using it to give me four sessions at once.

I eventually just memorized the key sequence to get four evenly divided sessions going.

[CTRL]+[a] – (Enter the command mode.)
[SHIFT]+[s] – (Split the window horizontally.)
[CTRL]+[a] – (Enter the command mode.)
[SHIFT]+[\] – (Split the window Vertically.)
[CTRL]+[a] – (Enter the command mode.)
[TAB] – (Move to the next window.)
[CTRL]+[c] – (Launch a shell in the current window.)
[CTRL]+[a] – (Enter the command mode.)
[TAB]- (Move to the next window.)
[CTRL]+[a] – (Enter the command mode.)
[CTRL]+[c] – (Launch a shell in the current window.)
[CTRL]+[a]  – (Enter the command mode.)
[SHIFT]+[\] – (Split the window Vertically.)

References:
https://www.gnu.org/software/screen/manual/screen.html