keys VS sops

The only one I've seen that comes close is https://keys.pub/ but it still misses a lot of what keybase gives (sigchains, etc.)

Previous HN thread: https://news.ycombinator.com/item?id=22995792

Are there any others to consider? It's been quite sad to see Keybase so stifled after being acquired. :-(

Do you think it's worth checking alternatives like https://keys.pub/ or https://keyoxide.org/?

One of the best features from Keybase (personally), is the ability to link identities across multiple different web entities, being able to prove "diggan" on Hacker News is indeed the same as "victorb" on GitHub, for example.

Seemingly, we're getting closer and closer to Keybase shutting down, considering the non-activity since the Zoom acquisition.

Previous threads have mentions of services like https://keys.pub/ and alike, but AFAICT, it doesn't actually provide "cross-service" proofs like Keybase does, and is mainly about managing key signing and related use cases.

What alternatives are online and viable to use today, for the purpose of "proving" that identities across different web properties are the same?

Suppose you only want a replacement for the key management part of keybase, what is there to be recommended? I know of https://keys.pub/ and https://keyoxide.org/ but the former (from someone ex-keybase) has no recent activity and a "not audited" warning, which at least is good to see.

There's also https://keys.pub/ (from someone ex-Keybase, if I remember correctly). I haven't looked at either closely. Can anyone compare and contrast?

I've been a supporter and user of keys.pub for a long time.

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

I've found this is largely solved by strictly separating plain config and secrets, and then having secrets pull from GCP secret manager / vault / whatever.

You can then commit all the config (including the secret identifiers) and it all just works so long as you're authenticated with your secret storage system.

We do this for the live configuration as well in line with Gitops and find it to work well.

If you don't want to use a cloud secret manager you can also use something like https://github.com/getsops/sops to commit the encrypted secrets safely

Basically, the simpler the better --just encrypt your secrets and check them in to version control.

We use SOPS[0] for this, and have found it to be pretty nice.

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

The answer is that secrets shouldn't be stored in the git repo at all, but somewhere safe like a password manager or Mozilla's SOPS which people seem to love.

Unfortunately, the SOPS project is in some sort of a limbo state and there has been quite a long period with limited maintenance and unclear position from Mozilla. Despite the project being accepted into the CNCF, it's still unclear what will happen with it going forward.