Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A question about keys. #85

Closed
aug24 opened this issue Feb 5, 2014 · 2 comments
Closed

A question about keys. #85

aug24 opened this issue Feb 5, 2014 · 2 comments

Comments

@aug24
Copy link

aug24 commented Feb 5, 2014

I'm trying to understand exactly how I can use chef-vault in our environment.

Can you clarify what key is used to encrypt/decrypt on a client when I specify encrypt for all clients of type X please?

  • Is it the chef client.pem? If not, what key is it, and where is it stored?
  • What happens if I create a new client of type X? Do I need to re-encrypt the vault for my new client to gain access?

Many thanks, and apologies if this is documented somewhere I haven't found.

@techish-io
Copy link

1- data bag item is encrypted with public keys of a) clients listed in -S (search) option, b) users listed in -A (admins) option. Public keys are stored on CHEF server.

And then decrypted with corresponding private keys of the same which is the one mentioned in knife.rb - And yes it is client.pem on a node if you aren't using a different key name with -K option.

2- a node of type X which was created after the vault item won't be able decrypt as it won't be listed in clients automatically. You have two options here

a) run knife encrypt/vault update command manually to add the new client
b) Have a periodically running process to do what is mentioned in "a" so new client gets added automatically.

Hope this helps!

@aug24
Copy link
Author

aug24 commented Feb 5, 2014

Perfect, thank you. That's what my team had concluded must be the case, but we wanted to be absolutely sure.

@aug24 aug24 closed this as completed Feb 5, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants