Security on Cesar Gimenes

An encrypted vault in Go

crg@crg.eti.br (Cesar Gimenes) — Sun, 31 May 2026 01:02:01 -0300

Let’s put together the three previous pieces:

A SQLite database that lives in RAM and, on disk, exists only as an encrypted blob.

The database runs in :memory:. On exit, we take a snapshot of the database bytes, encrypt it with the password, and write it out. On startup, we read the blob, decrypt it with the password, and deserialize it back into RAM.

Protecting Credentials and Configurations with an Encrypted Container.

crg@crg.eti.br (Cesar Gimenes) — Thu, 20 Feb 2025 22:43:56 -0300

I use a small pocket computer in my backpack. This device is used for testing and development, and it stores sensitive information such as credentials, passwords, and access keys. I don’t want this data to fall into the wrong hands. Unlike my laptop, which has an encrypted drive, my pocket computer’s drive isn’t encrypted. Drive-wide encryption consumes a lot of processing power and usually requires disabling SSD TRIM, which hurts performance.

Fork Bomb: From Code to Defense

crg@crg.eti.br (Cesar Gimenes) — Sat, 04 Jan 2025 11:48:47 -0300

The first time I heard about fork bombs was a long time ago. Although I found it fascinating that a piece of code could spawn two more processes of itself, causing exponential process growth and eventually freezing the system, I didn’t believe it was a viable attack until I discovered how many systems are vulnerable to code injection.

What is a fork bomb?

In general terms, a fork bomb is code that spawns processes recursively. The first process spawns copies of itself, those copies spawn more copies, and so on, until the system runs out of resources and freezes. The result is a DoS (Denial of Service) attack.