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

How to deal with sensitive data #8

Open
rogeriochaves opened this issue Jun 7, 2016 · 1 comment
Open

How to deal with sensitive data #8

rogeriochaves opened this issue Jun 7, 2016 · 1 comment

Comments

@rogeriochaves
Copy link
Contributor

rogeriochaves commented Jun 7, 2016

Does kickstart have a recommendation or helpers for dealing with sensitive data? If not, should it?

I suggest to use gpg, like this:

gpg --symmetric --cipher-algo aes256 id_rsa

And then decrypt it like this:

gpg --decrypt --passphrase "$KICKSTART_DECRYPT_KEY" files/.ssh/id_rsa.gpg

Where KICKSTART_DECRYPT_KEY could be in the environment or read from the user at runtime

cough much easier than chef knife data bag shenanigans cough

@bltavares
Copy link
Owner

Hey @rogeriochaves,

Thanks for the idea. I think there could be a gpg helper module with those patterns. I'm not sure if aes256 is the best option as I'm not an specialist on this.

It is already possible to read a value interactively over the tunnel, so using a read -p KEY on the script would be enough to have it available on the target host. There is an example of requesting a value on tty.space

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants