How to store and retrieve my secrets in a linux server? (lemmy.pe1uca.dev)

submitted 1 year ago by [email protected] to c/[email protected]

13 comments fedilink hide all child comments

All guides to deploy using docker mention typing your keys/credentials/secrets into the docker compose file, or use a .env or similar file, I'm wondering how secure is this and if there's a better option.

Also, this has the issue of having to get into the server to manage them, remembering which file has each credential.

Is there a selfhostable secrets manager? I've only found proprietary/paid ones for large infrastructures and I just need it for a couple of my servers/projects.

you are viewing a single comment's thread
view the rest of the comments

[-] [email protected] 1 points 1 year ago

I wish there was something between hashicorp vault and keepass. I want a nice simple UI that even my family could use with Terraform integration. Anyone know of such a program?

[-] [email protected] 7 points 1 year ago

I have no experience with terraform but Bitwarden has an API and CLI, so you might be able to script something with it?

[-] [email protected] 2 points 1 year ago

Thanks. I knew about bit/vaultwarden but I just looked and I see that there is a Terraform module and the UI looks good.

Thanks.

[-] [email protected] 1 points 1 year ago* (last edited 1 year ago)

I was thinking about this, since it'd be using foss, but if no library exists to handle the pass to a script/config file then it'd be maintaining a custom solution which might not be that secure.

Edit: hashicorp's vault is open source, so I'll be giving it a try.
https://github.com/hashicorp/vault

[-] [email protected] 0 points 1 year ago

Bitwarden has a CLI that you can script with. Also vaultwarden is the FOSS version.

Just in case you want to try.

this post was submitted on 14 Jul 2023

15 points (89.5% liked)

Selfhosted

39257 readers

234 users here now

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:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]