sops VS age

How does this compare to mozilla's sops[1]. I've heard sops is also used for this kind of usecase, although it seems to do much more.

[1] https://github.com/getsops/sops

You can also do some nice things with https://github.com/getsops/sops, I store encrypted password and secrets on git with sops, but I also use nix so I have near perfect integration with my services.

SOPS is a simple, yet powerful tool for managing secrets. It consumes a clear secret file in various formats and encrypts values using keys. The encrypted file can be then stored in a version control system and decrypted when needed.

There's also sops: https://github.com/getsops/sops

I've used it at two jobs now over about 5 years and have had zero issues.

My script just sets up default .sops.yaml for https://github.com/getsops/sops

You can further edit .sops.yaml(eg have multiple of them) and decide how you split secrets in your directory tree to further customize who can decrypt the secrets.

It works pretty well for prod/dev splits, etc

Mozilla SOPS (Secrets OPerationS) is an open-source command-line tool for managing and storing secrets. It uses secure encryption methods to encrypt secrets at rest and decrypt them at runtime. SOPS supports a variety of key management systems, including AWS KMS, GCP KMS, Azure Key Vault, and PGP. It's particularly useful in a DevOps context where sensitive data like API keys, passwords, or certificates need to be securely managed and seamlessly integrated into application workflows.

Encrypted secrets thanks to SOPS and Age

We do the exact same thing to keep track of some credentials we use sops[1] and AWS KMS to separate credentials by sensitivity, then use the git differ to view the diffs between the encrypted secrets

Definitely not best practice security-wise, but it works well

[1] https://github.com/getsops/sops

For anyone new to SOPS like I was - https://github.com/getsops/sops

It looks like age with SSH keys uses a birationally equivalent keypair.

https://github.com/FiloSottile/age/blob/176e245b3cb3ada322c2...

If you're using, for example, libsodium, you'd want the Ed25519 to X25519 functions to convert the two. (Note that you need to operate over raw bytes to do this.)

In practice, you shouldn't do this. Use different keys for different purposes!

I migrated to chezmoi recently my only gripe is `chezmoi cd` opening in a new shell but `chezmoi git` usually is what I need. The age [0] integration is nice.

[0] - https://github.com/FiloSottile/age

I believe there is `pass-age` https://github.com/FiloSottile/passage ... unifies to `ssh` keys as the key material.

https://github.com/FiloSottile/age

```

I have been a fan of https://github.com/FiloSottile/age for a while now, but one thing that has always bothered me about encryption tools is how they don't offer a way to secure a whole directory which, IMO, is a much more common use-case.

I decided to spend a couple hours tackling the problem myself and came up with agevault.

It's a directory encryption tool using age file encryption. It locks/unlocks a vault (directory) with a passphrase-protected identity file and like age, it features no config options, allowing for a straightforward secure flow.

I'll answer any questions regarding it. As always, use it at your own risk.

Identity files can be passphrase encrypted and cmd/age will transparently ask for the passphrase before using them. Is that what you meant?

https://github.com/FiloSottile/age?tab=readme-ov-file#passph...

I would love to see this used in a FIPS-compliant variant of age[1] for archival file encryption use cases. We had banking industry auditors veto age for this use case due to the use of ChaCha instead of AES (they were fine with the X25519 public key part of age which I think was somewhat recently approved by NIST).

I’ve no experience with golang but it seems like it should drop right in based on the age spec. I might give it a shot if time ever permits. I guess I should call it “cage” as in “compliant actually good encryption”

1: https://github.com/FiloSottile/age

age

and echoing the result after converting to an age private key