encpass.sh VS transcrypt

https://github.com/plyint/encpass.sh/archive/v${pkgver}/${pkgname}-${pkgver}.tar.gz

The difficulties mentioned in the article with passing secrets on the command line is one of the reasons why we wrote encpass.sh (https://github.com/plyint/encpass.sh). We had a similar need for a lightweight solution for managing secrets for simple shell scripts on our local workstations and in restricted environments. Bonus, it can be easily customized with extension scripts to adapt functions for your own specific needs. See our keybase extension for an example -> https://github.com/plyint/encpass.sh/blob/master/extensions/...

We made an extension for encpass.sh that stores secrets in Keybase (https://github.com/plyint/encpass.sh/blob/master/extensions/...) if that sort of thing is of interest to you. Outside of personal secrets, it can be used as a sort of low cost stand in for shared secrets that you might use something like Vault for in a team environment.

I was looking into secret storage in git recently and rather liked Transcrypt: https://github.com/elasticdog/transcrypt

On the actual system itself (you likely know this as you'd mentioned reading other posts, but) I have Neovim compiled on my phone (directly through Termux), notes pushed up to Github using transcrypt for backups and live-synced between several devices using syncthing (which is how I get notifications on my phone, using a Raspberry Pi and systemd services to implement against orgmode.nvim's notification API).

I use nvim-orgmode on my computer through Neovim, and keep that pushed up to Github (encrypted using transcrypt) but also have a Syncthing server setup on a Raspberry Pi.

Also if you want the notes to be encrypted and you push them to Github, try transcrypt. They won't be encrypted on disk, but will be when you push them.

Start writing all of your work down. I personally put almost every line of code I ever write into github. I have a "misc" project for random one-off things, but I always commit it to a repo. I started doing this in 2013/2014 and its been incredibly valuable to go back and refer to old work (its also fun to see how far you've come). This gets interesting when you start needing to write down information that shouldn't be public (e.g. api keys). You're into crypto, so you can probably see the fun in this. I've use a program called transcrypt to store encrypted files in my git repos. Be careful with transcrypt though, if you make a mistake you can accidentally publish secrets in plain text, and it does open you up to brute force attacks.