Encryption: What It Is and What I Actually Use

The Idea, Stripped Down

Encryption takes readable data and transforms it with a key so that without the key it is noise.

The classic teaching example is a shift cipher: move every letter forward one place. a becomes b, b becomes c, so example becomes fybnqmf. That is genuinely encryption, and it is genuinely useless, because there are only 25 possible keys and a computer tries all of them before you finish reading this sentence.

Real encryption differs in two ways that matter. The key space is so large that brute force is not an option, and the algorithms are designed so that the ciphertext leaks nothing about the plaintext — no patterns, no letter frequency, no length clues beyond the message size. When people say "military-grade", that is roughly what they mean, though the phrase itself is marketing rather than a standard.

A photorealistic shot of an external hard drive and a laptop on a desk, a sticky note with a handwritten sequence of characters partly visible and blurred, warm desk lamp light, realistic photography, no legible text.

Why I Encrypt Everything Now

I did not always. The change came from a simple question: what happens if this laptop is stolen from a car park?

Without full-disk encryption, the answer is that the drive comes out, goes into another machine, and everything is readable. Not "hackable" in a movie sense — just readable. Email archives, tax returns, family photos, saved passwords in the browser, the notes app where you wrote down something private in 2019 and forgot.

Full-disk encryption changes that outcome completely. The drive is useless without the password, and the attack surface drops from "anyone with a screwdriver" to "someone who also has your password". That is the whole argument, and it is why I now consider it the single most valuable security setting on any machine I own.

The critical limitation, and people miss it constantly: disk encryption protects data at rest, not a running machine. Once you have unlocked it, everything is plaintext, and any process running as you can read it. Encryption does not stop malware. It stops theft.

What I Use, By Platform

Windows: BitLocker. Built in, free on Pro editions, and the default on many modern machines. Turn it on, save the recovery key somewhere that is not the machine itself — a password manager entry is fine, a text file on the encrypted drive is not. If you lose the recovery key and the machine needs a motherboard repair, the data is gone permanently. That is the feature working, and it is also the most common way people lose everything.

macOS: FileVault. Same idea, on by default in recent versions. The recovery key handling is the same warning: store it off-device.

Linux: LUKS. Set up at install time, which is why the decision matters at that moment. Adding LUKS to an existing unencrypted root is possible but painful; encrypting /home separately or using a container file for sensitive data is the pragmatic retrofit.

Portable drives: VeraCrypt. This is the successor to TrueCrypt, which is the important correction to make. TrueCrypt was abandoned in 2014 and later audited with serious flaws found; it should not be used, and any guide still recommending it is out of date. VeraCrypt is the maintained fork, supports the same container files, and is what I use for a USB stick that carries anything sensitive.

A photorealistic close-up of a laptop screen showing a disk encryption setup dialog with a recovery key displayed, a USB stick plugged into the side, notebook beside it, soft daylight, realistic photography, no legible text.

Encrypting Files Rather Than Drives

Sometimes you want one file or one folder encrypted, not the whole disk. Two good options:

age — a modern, simple file encryption tool. One command, one key, and the format is deliberately boring:

age -r <recipient-public-key> -o backup.tar.gz.age backup.tar.gz
age -d -i key.txt backup.tar.gz.age > backup.tar.gz

GPG — older, more capable, and considerably easier to misuse. If you already have a key and understand it, use it. If not, age is the better starting point.

For cloud storage, the pattern that works is encrypting before upload rather than trusting the provider's "encrypted at rest" claim. That claim is usually true and also usually means the provider holds the key, which is not the same threat model as you holding it. rclone has a crypt backend that does this transparently on top of any provider.

A photorealistic shot of a person's hands typing a long passphrase into a laptop at a kitchen table, a password manager app open on the screen, morning light through a window, realistic photography, no legible text.

The Things Encryption Will Not Save You From

A weak password. Full-disk encryption is only as strong as the passphrase that unlocks it, and an attacker with the drive has all the time in the world to guess offline.

A running, unlocked machine. Covered above, worth repeating.

Phishing and malware. Encryption is not a control against code that runs as you.

Losing the key. This is the one that actually happens. Every encryption setup has a recovery path; write it down, store it somewhere that is not the encrypted device, and test that you can retrieve it before you trust it with anything you cannot recreate.

What I Would Do If You Only Do One Thing

Turn on the built-in full-disk encryption on your main machine today, and put the recovery key in your password manager. It takes ten minutes, it costs nothing, and it converts "my laptop was stolen" from a catastrophe into an inconvenience.

Then, if you carry sensitive files on removable media, use VeraCrypt containers for those. Everything beyond that is refinement.

Don't trust the download button. Trust the hash.

If this was useful, More hands-on tech guides at TechGeek. No pressure — read it whenever it's useful.


Luke Keam
Spot a bug or want a custom utility built? I'd love to hear from you. Get in touch
Luke Keam | techgeek.biz