Jira (HI-633) Content from eyaml should be Sensitive by default

[Pat Riehecky (Jira)]

Pat Riehecky created an issue

Hiera / HI-633 Content from eyaml should be Sensitive by default Issue Type: Improvement Assignee: Unassigned Created: 2022/09/19 8:00 AM Priority: Normal Reporter: Pat Riehecky When content is decoded from an `eyaml` backend, hiera should automatically mark it as a Sensitive data type.  Currently it is just converted to the backing data type. This can lead to unintended disclosure of the encrypted values within modules. Add Comment

This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)

[Henrik Lindberg (Jira)]

Henrik Lindberg commented on HI-633

Re: Content from eyaml should be Sensitive by default This would need to be done in the eyaml module since it can read plain yaml as well as the specially encoded eyaml content. Many users rely on eyaml backend to also read plain text so cannot be done in hiera as it would not know if the source was encoded or not.

Add Comment