There is this tool called age written in go and a fully compatible Rust implementation called rage. They promise to be a simple tool for encrypting files and other things.
It only does encryption, using public key cryptography (Curve 25519 or SSH keys) or password based symmetric encryption. (Please excuse me glossing over some details here)
It only encrypts things, no signatures beyond AEAD involved. It aims to be minimalistic and do just one thing reasonably well instead of being a mediocre multi tool. It doesn’t aim to be a full replacement for things like OpenPGP.
AFAICT there hasn’t been a proper security audit yet. There seem to be some issues with the design as pointed out here which don’t look like critical flaws to me, but then again I’m not a cryptography expert.
Some of the questions I want to throw into the discussions are:
- Is it any good?
- In which situation would you use it?
- What are some alternatives that do it differently or maybe even better and why is that?
Bonus question: Is there a similar tool that uses an audited library like libsodium, and if not, would it be worth developing one?
libsodium-file-crypter hasn’t received any commits in the past 4 years. Looks abandoned to me.
Or no one found something. Commit history is not an indicator that no one is working on something, more like that no one submitted something. If its finished, then there is no need to commit something.
I could post an list of tools designed for enterprise environment users. There are not man because in such an environment you basically only use audited programs due to assurance company reasons, in case there are problems because the first and last question is if issues were known and if that could have been prevented.
You can also inspect open audit databases and check what was audited already.