Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

So you still need a secret when provisioning, and you need to handle change management for that, and storing it securely outside of the git repo. And agenix did not change that workflow, or did it?


Yes and no.

I only need to care about my SSH key(s). Which I had to anyway. But now the secrets for all the services (except SSH) lie right besides their config. Any change in one or other is directly visible in git log.

In short, age cut down on the number and types of secrets that I have to manage out of band. Which is very good. It's always easier to be able to remember 2 things (config + SSH keys) than 2+n things (config + SSH keys + whatever secret mechanism any service uses, times number of services).


You could also include SSH keys as public secrets.

https://github.com/Foxboron/ssh-tpm-agent




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: