Re:Protecting infrastructure secrets with Keywhiz from Square
by sul3n3t on Tuesday April 14, 2015 @03:01PM
(#9376518)
Keyczar is meant to solve a different problem. It’s meant to be a simple programmatic API for crypto operations, while being high-level and excluding unsafe options. NaCl (http://nacl.cr.yp.to/) has similar goals to Keyczar.
Keywhiz isn’t an interface for software to do crypto. Rather, it’s a system to manage the secrets/keys used for crypto and making them available to the services that need them. It doesn’t explicitly look at the content of secrets, unless a plugin is used.
Re:Protecting infrastructure secrets with Keywhiz from Square
by ispivey on Tuesday April 14, 2015 @03:08PM
(#9376559)
Understood! I'd looked at Keyczar in the past as a component of a system to manage secrets/keys, but I see it's actually providing about 0% of what Keywhiz does.
Re:Protecting infrastructure secrets with Keywhiz from Square
by amenghra on Tuesday April 14, 2015 @02:22PM
(#9376262)
Filesystem interface just by itself is a big difference.
Keywhiz lets you manage things like mysql or other configs which might contain things like username/passwords, passwords to unlock certificates, API keys, etc. If you don't have the resources/option to modify applications to use a specific API, the filesystem might be your only viable solution.
Obvious pieces to me appear to be (1) roles and auditability (2) end-user front-end (3) filesystem interface & associated ease of access for various services. But I'm not an expert!