Rudric: Simple secrets management solution. Stop putting secrets in .env!

90 points yuuuuuuuut

Rudric

https://github.com/mike-lloyd03/rudric

Announcing Rudric, a simple secrets management CLI tool meant to keep sensitive data out of .env files.

I wrote this because I realized I had .env files spread all over my filesystem with sensitive data like API tokens and service account passwords. .env files are really convenient, but not wise if they jeopardize security.

Instead, why not keep using the idea of a .env file but store secret data in an encrypted form on disk?

Enter Rudric, the Keeper of Secrets. This simple CLI tool will allow you store secret data in encrypted form on disk and easily decrypt and set the secret values in your environment.

Instead of a .env file with sensitive data in it, you'd have a .renv file with the secret names instead:

GITHUB_TOKEN={{personal_github_token}}
GITHUB_API=https://api.github.com
DATABASE_URL=postgres://{{pg_user}}:{{pg_pass}}@localhost:5432

Upon running rudric env | source, you will be prompted for your vault password, the secret names will be decrypted and set as environment variables in the current shell session. No need to persist these secrets on disk in clear text.

Secrets can be edited and renamed after creation and will be done using your default EDITOR (or VISUAL) programs. You can even set a session variable to avoid having to type your password repeatedly.

The program uses slick TUI crates like dialoguer to make interacting with the CLI feel clean and modern.

This is the first open-source project I've advertised to the community so feedback is greatly welcomed.

Also, this isn't intended to be a full-on password manager like BitWarden, 1Password, or Proton Pass. It's merely a way to help devs maintain good security practices.

And I know similar tools exist like pass. This isn't an attempt to replace it or RIIR. I'm just offering a slimmed down alternative.

Thanks!