The Digital Bunker: Command Line Comfort

Security must be usable. Typing file paths is tedious and prone to error. This guide shows you how to use aliases to integrate your encryption scripts directly into your terminal workflow on both Linux and GrapheneOS (via Termux).
The Digital Bunker: Command Line Comfort

Turn your scripts into native commands using Bash aliases

by Alien Investor

────────────────

“Complexity is the enemy of security.” But friction is the enemy of adoption.

If protecting your data feels like a chore—typing long paths like ~/Scripts/encrypt-folder.sh every time—you might skip it “just this once.” That is when you get vulnerable.

In Part 1 and 2, we built robust encryption scripts. Now, we integrate them into your system so they feel like native commands.

We don’t need GUIs or taskbar icons. We use aliases.

────────────────

The Concept An alias is simply a custom nickname for a command line instruction. Instead of typing the full path to your script, you just type encrypt. The shell handles the rest.

This works the same way on your Linux desktop and inside Termux on GrapheneOS.

────────────────

Step 1: Locate your config Your terminal (shell) has a configuration file that loads every time you open a new shell session.

  • Bash users (common on most Linux/Termux): ~/.bashrc (Note: login shells may use ~/.bash_profile, which often sources ~/.bashrc.)

  • Zsh users (default on macOS; common on some Linux setups): ~/.zshrc

To find out what you are running, type:

Bash

echo $SHELL

────────────────

**Step 2: **Set the alias Open your config file with a text editor (e.g., nano).

On Termux or standard Ubuntu/Debian (Bash):

Bash

nano ~/.bashrc

Scroll to the very bottom of the file and paste the following lines (assuming you saved your scripts in a folder called “Scripts” as recommended in Part 2).

> Note: The # at the beginning is important—it marks the line as a comment so the terminal doesn’t try to execute the text.

Bash

# --- Alien Investor Security Aliases ---
alias encrypt="~/Scripts/encrypt-folder.sh"
alias decrypt="~/Scripts/decrypt-folder.sh"

Make sure the scripts are executable (if you haven’t done this already):

Bash

chmod +x ~/Scripts/encrypt-folder.sh ~/Scripts/decrypt-folder.sh

Save the file (CTRL+O, Enter) and exit (CTRL+X).

────────────────

**Step 3: **Activate For the changes to take effect, you must reload the configuration (or simply restart your terminal).

Run (pick the file you edited):

Bash:

Bash

source ~/.bashrc

Zsh:

Bash

source ~/.zshrc

────────────────

The Result Now, your workflow is seamless.

To Encrypt: Open your terminal and simply type:

Bash

encrypt

The script launches immediately.

To Decrypt: Navigate to the relevant folder and type:

Bash

decrypt

By reducing the friction of entry, you make security muscle memory, not a task.

────────────────

The Digital Bunker Series Complete your setup with the scripts from the previous parts:

Part 1: Desktop Sovereignty (Linux) https://primal.net/Alien-Investor/the-digital-bunker-scripting-sovereignty

Part 2: Mobile Sovereignty (GrapheneOS/Termux) https://primal.net/Alien-Investor/the-mobile-bunker-encryption-on-grapheneos-termux-edition

────────────────

Money, power, Bitcoin — and OPSEC. I write about financial sovereignty, privacy, and cybersecurity in a world built on control. More at alien-investor.org 👽 (German Only)


No comments yet.