Environment & Shell Customization (Aliases/Functions/.Bashrc)

Stop your shell history from leaking sensitive secrets

🧩 The Challenge

Everyone has accidentally typed a database password or an API key directly into the terminal while rushing. It sits there in your .bash_history forever, waiting for a bored intern or a security audit to find it.

💡 The Fix

You can tell your shell to ignore commands that start with a space or match specific patterns. It’s a simple change to your shell config that saves you from yourself.

HISTCONTROL=ignorespace:erasedups
export HISTIGNORE="ls:pwd:exit:history:clear:mysql -u* -p*"

⚙️ Why It Works

Setting HISTCONTROL to ignorespace means any command you prefix with a space won’t get saved, and the HISTIGNORE list lets you block specific sensitive patterns entirely. That tiny space character before your command is a lifesaver when you’re pasting credentials in a hurry.

🚀 Pro-Tip: If you already have secrets in your history file, just open it in vim and delete the lines before they sync to your central log server.

Linux Tips & Tricks | © ngelinux.com | 11/3/2026