Closed igalic closed 3 years ago
@igalic Thanks for reporting this ... indeed the current solution cannot fix all misconfigurations, but I doubt this can be solved easily. For this to work you would have to define a sane file mode for all relevant files on all supported distributions ... we could limit this (for now) to /etc/crontab, but what about the rest of files / directories we manage?
Describe the bug
Let's assume someone ("accidentally") set a funky mode for
/etc/crontab
, such as5777
. Since our code sets the mode relatively:This can lead to unexpected or at least unwanted results.
Expected behavior I want the file modes to be deterministic, no matter what their (wrongly) pre-configured state.
Actual behavior
After applying
our
crontab
now like this:which is still wrong.
OS / Environment
Red Hat Enterprise Linux Server 7.6
Puppet Version