It's based on ChaCha20-Poly1305 AEAD and the author is well respected in the crypto community.
It's based on ChaCha20-Poly1305 AEAD and the author is well respected in the crypto community.
"You cannot visit age-encryption.org right now because the website uses HSTS."
FYI, no I'm not in the millitary/intelligence agency. I'm just a software developer who like to send, say source codes or documents securely.
I'm however interested in something as small as possible, with minimal number of dependencies and implemented in C. Yes I know it's an old language with its own issues. But C is the "highest level" I at this moment consider acceptable for something that should be a competition to GPG.
Age also has a spec, so it can be reimplemented in other languages: https://age-encryption.org/v1
There's already a Rust implementation: https://github.com/str4d/rage
The other languages could be used for the "proof of concept" implementation or with which the additional comparison tests could be performed, but having C as the most important version is unavoidable.
Something that surprised me when I researched this (I wrote a similar tool internally at my last job, along with writing a blog post about the inadequacy of PGP) is that general-purpose encryption doesn't really have as many use cases as you'd assume. The reason for that is that modern cryptosystems are purpose-built for applications. Messaging cryptography (and email is a messaging system!) is different from backup cryptography, which is in turn different from disk cryptography.
Probably single most common application of general-purpose cryptography is for cryptographic tokens (most common subset: cookies). But even there, your cryptography tends to be specialized, in terms of what it doesn't have --- in particular, metadata, which tends to be an antifeature for tokens.
(I like Age a lot and you should use it if it makes sense for your application, though plain-ol'-secretbox is probably the right call for your encrypted cookie).