Skip to content

Conversation

@watologo1
Copy link

If tuned creates /var/log/tuned
permissions are now 750 instead of 755

CC: Matthias Gerstner [email protected]

If tuned creates /var/log/tuned
permissions are now 750 instead of 755

CC: Matthias Gerstner <[email protected]>
@olysonek
Copy link
Contributor

I'm still missing a justification why the directory should not be world-readable. This will hurt user experience, so it needs to be well justified.

@watologo1
Copy link
Author

I tried to find a hint on FHS (Filesystem Hierarchy Standard), but I couldn't find a hint about permissions for this directory.
IMO it makes a lot of sense to remove the world readable/access bits on systemd service logfiles.
Matthias Gerstner who suggested this, arguemented (I'll add him):

We try to harden our distributions with regards to log file permissions. In short, we want to avoid
world readable log files, because they might at some point contain sensitive data that could facilitate
other types of attacks.

@mgerstner
Copy link
Contributor

Basically this is a hardening measure we're currently following up in SUSE distributions. Trigger for this was an older security finding, where passwords got exposed in log files.

I don't know whether Fedora/Red Hat products by know implement the suggested "secure by default config and log file permissions" policy refered to in above post. Maybe it's something not for upstream but only for distro adjustment. In the latter case it would help if the used permissions could be a compiler or config file setting that can easily be adjusted in packaging.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants