isomorphic-webcrypto VS pass

End to end encryption, if possible: if your use cases allows it, try your best to implement end to end encryption. That means that, if the user uploads a file, it should be encrypted client side (in the browser) before uploading. You can derive the key from the user's password and/or security token (see below). Check here for some resources: https://www.w3.org/TR/WebCryptoAPI/.

https://en.wikipedia.org/wiki/Argon2

> There is no reason not to use Argon2

In this case, the reason for not using Argon2 is that it's not available: https://www.w3.org/TR/WebCryptoAPI/

> Well if this product isn't for mass-market

This is a demo for self-contained HTML encrypted secrets. Do with it what you want.

A TypeScript Hybrid Public Key Encryption (HPKE) implementation build on top of Web Cryptography API This module works on web browsers, Node.js, Deno and Cloudflare Workers

I haven’t used it, but https://github.com/kevlened/isomorphic-webcrypto might be more along the lines of what you’re after

Age is amazing. I'm using a Yubikey in conjunction with it to encrypt {passwords, docs} and commit them to a private GitHub repo.

See here if interested: https://github.com/mihaigalos/pass

I backup everything directly to GitHub. I first encrypt/seal my passwords/files using a Yubikey+PIN then git push them.

Here's my take on the automation: https://github.com/mihaigalos/pass