sops
client
Our great sponsors
| sops | client | |
|---|---|---|
| 150 | 44 | |
| 15,114 | 8,756 | |
| 2.7% | 0.5% | |
| 9.0 | 9.7 | |
| 4 days ago | 5 days ago | |
| Go | Go | |
| Mozilla Public License 2.0 | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sops
-
Pico.sh – Hacker Labs
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
-
Encrypting your secrets with Mozilla SOPS using two AWS KMS Keys
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.
-
An opinionated template for deploying a single k3s cluster with Ansible backed by Flux, SOPS, GitHub Actions, Renovate, Cilium, Cloudflare and more!
Encrypted secrets thanks to SOPS and Age
-
Tracking SQLite Database Changes in Git
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
-
The Twelve-Factor App
For anyone new to SOPS like I was - https://github.com/getsops/sops
- Storing and managing private keys
-
Show HN: Shello – Wrangle Environment Variables
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
-
Check your secrets into Git [video]
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
-
How to secure secrets of docker-compose stacks with git?
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.
-
Is it safe to commit a Terraform file to GitHub?
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.
client
-
Ask HN: What are these Keybase URLs I see in many HN profiles?
https://github.com/keybase/client/graphs/code-frequency tells the story well.
-
Is Keybase dead?
There have been 17 releases since Keybase was acquired
-
Error 202 is your device revoked?
https://github.com/keybase/client/issues/19655 https://www.reddit.com/r/Keybase/comments/k9d57l/how\_do\_i\_avoid\_being\_locked\_out\_error\_202/
-
Keybase.pub Shutting Down on March 1 2023
> development slowed down to a crawl
It's pretty wild that you can see exactly the moment when Zoom bought them on their github activity graph: https://github.com/keybase/client/graphs/code-frequency
- Status of Keybase
-
Ask HN: What's the status of Keybase after Zoom acquisition?
GitHub contributions to master branch of keybase/client: https://github.com/keybase/client/graphs/contributors
-
keybase.pub cert expired — can someone look at this please?
Reported it here : https://github.com/keybase/client/issues/25398
-
Is there a RAT in Keybase?
The moment Zoom took over, contributions to the project effectively collapsed.
-
Is Keybase still trusted and recommended or should one stop using Keybase after they were acquired by Zoom, which has ties with China?
Active development stopped the day Keybase was acquired: https://github.com/keybase/client/graphs/contributors 3700+ open issue tickets, most have no responses by a maintainer: https://github.com/keybase/client/issues
What are some alternatives?
sealed-secrets - A Kubernetes controller and tool for one-way encrypted Secrets
Peergos - A p2p, secure file storage, social network and application protocol
Vault - A tool for secrets management, encryption as a service, and privileged access management
osxfuse - FUSE extends macOS by adding support for user space file systems
age - A simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
upspin - Upspin: A framework for naming everyone's everything.
git-crypt - Transparent file encryption in git
git-remote-gcrypt - PGP-encrypted git remotes
terraform-provider-sops - A Terraform provider for reading Mozilla sops files
threema-android - Threema App for Android.
vault-secrets-operator - Create Kubernetes secrets from Vault for a secure GitOps based workflow.
Rundeck - Enable Self-Service Operations: Give specific users access to your existing tools, services, and scripts