Hi everyone, I was perusing through Conjur and Vault documentation, since I’m starting to think that learning a secret-management system might be a worthwhile investment with the app secrets and SSH keys and CA certificates around.
I was wondering, what do you use in your network? I plan to take a look at Teleport’s documentation too, was curious about what the community uses at home.
Pass works decently for us (fine except for the GPG key management aspect really) and allows us to have our Puppet config management write new secrets easily and read secrets for config file generation and similar purporses.
How do you securely authenticate, restrict access to secrets and store secrets with pass? Other than GPG authentication and discrete keys for different secrets (in which case, how would you automate key policies and life cycles?)
We do use GPG keys that are essentially signed by one of our admin keys which is set to fully trusted on the client machines so that keys it signs are trusted with just the one signature. The keys themselves are generated with revocation certificates for those admin keys and a limited lifetime as well by our helper script. The signed keys are stored in the pass repository in a separate folder and the helper script has an idempotent import command which also checks a few other settings and common issues and generates missing revocation certificates after an admin key is replaced. Any automated changes in the repository itself (such as updating the .gpgid files in project directories to include all project members and reencryption afterwards) are made by our puppet master.
It certainly isn’t perfect but it works well enough.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
Pass works decently for us (fine except for the GPG key management aspect really) and allows us to have our Puppet config management write new secrets easily and read secrets for config file generation and similar purporses.
How do you securely authenticate, restrict access to secrets and store secrets with pass? Other than GPG authentication and discrete keys for different secrets (in which case, how would you automate key policies and life cycles?)
We do use GPG keys that are essentially signed by one of our admin keys which is set to fully trusted on the client machines so that keys it signs are trusted with just the one signature. The keys themselves are generated with revocation certificates for those admin keys and a limited lifetime as well by our helper script. The signed keys are stored in the pass repository in a separate folder and the helper script has an idempotent import command which also checks a few other settings and common issues and generates missing revocation certificates after an admin key is replaced. Any automated changes in the repository itself (such as updating the .gpgid files in project directories to include all project members and reencryption afterwards) are made by our puppet master.
It certainly isn’t perfect but it works well enough.