News for hackers. Stuff that matters.
Re:Summon – Get Your Secrets into Source Control by jessaustin on Friday December 04, 2015 @04:51PM (#10679415)
ISTM secrets should mostly be generated where they're needed and should not leave that location. If two locations need to interact then use asymmetric keys so that the public key may be shared. Of course such a system must be bootstrapped, but suitable arrangements will make that a relatively rare manual process.

Of course exceptions might be made for any number of operational reasons but I think it helps to at least aim for the right thing even if it isn't always possible. Secrets in VCS seems to be a shot in exactly the opposite direction.

Re:Summon – Get Your Secrets into Source Control by kgilpin on Monday December 07, 2015 @09:55AM (#10689816)
Summon puts secrets metadata into source control; not actual secrets.
Re:Summon – Get Your Secrets into Source Control by jessaustin on Monday December 07, 2015 @11:01AM (#10690197)
Haha it seems the motto should instead be "get some pointers to your secrets into source control". This makes the tool much less vulnerable to the abuse I was envisioning, but also pushes it into "so what?" territory for me. I can already save pointers to secrets in my code; this is another layer of configuration for dubious benefit.
Re:Summon – Get Your Secrets into Source Control by kgilpin on Monday December 14, 2015 @01:33PM (#10732825)
Summon also fetches the secrets out of the backend in a provider neutral way; it's well documented; and it ensures that secrets stay off persistent disks. So those are the reasons to use it. It's better for the world if there are a smaller number of doing the same things.