Backport of cmd/tls: set explicit file permissions for generated certs into release/1.20.x #22366
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Consul CLI's tls create command was generating some sensitive files (e.g. consul tls ca create -server) that had excessive permissions at 0666 for public certs created and it should be 0644. Updated the code to use 0644 file perms when creating sensitive files with ca and certs.
NOTE: disabled Compatibility Integration Tests until pipeline upgrade is in place
Testing & Reproduction steps
umask 000
consul tls ca create -domain=example.test
and list the directory to view generated files withls -lah
with excessive perms.consul tls cert create -server
to see similar resultsumask 022
Links
https://hashicorp.atlassian.net/browse/SECVULN-8634
PR Checklist