-
-
Notifications
You must be signed in to change notification settings - Fork 500
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
erlang_cookie echo'ed to agent output #837
Comments
It's been a while, but does anyone know the current state of the art about preventing sensitive information from being leaked? I know that Puppet has the "sensitive" type, but my memory is that, in the past, it was not actually that tricky to prevent things from being exposed. https://puppet.com/blog/my-journey-securing-sensitive-data-puppet-code/ has some info that may be useful. |
Override the is_to_s and should_to_s methods in the puppet property to make sure it's not shown in outputs. Closes: voxpupuli#837
Override the is_to_s and should_to_s methods in the puppet property to make sure it's not shown in outputs. Closes: voxpupuli#837
The usual method for a File resource is to pass the parameter "show_diff => false" but I'm not sure what this causes to happen internally or how to apply this technique to other resource types https://puppet.com/docs/puppet/latest/types/file.html#file-attribute-show_diff |
Override the is_to_s and should_to_s methods in the puppet property to make sure it's not shown in outputs. Closes: voxpupuli#837
Override the is_to_s and should_to_s methods in the puppet property to make sure it's not shown in outputs. Closes: voxpupuli#837
Since erlang_cookie is sensitive data (authentication credential for cluster members), it should not be shown in the output of puppet agent.
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
What are you seeing
What behaviour did you expect instead
The text was updated successfully, but these errors were encountered: