Skip to content

Conversation

@LordGrimmauld
Copy link
Contributor

setting LogsDirectory and RuntimeDirectory ensures systemd will create these directories ahead of starting the auditd service. It also ensures the auditd service has write permissions, even if someone might add additional hardening options to the systemd service in the future. As a result, there is just no more need for the tmpfiles rules.

@LordGrimmauld
Copy link
Contributor Author

We might also want to set LogsDirectoryMode / RuntimeDirectoryMode now that i think about this... The tmpfiles rules had 0700 for log dir. I am thinking the runtime dir should probably be 755 or 644.

This ensures systemd will create these directories
ahead of starting the auditd service. It also ensures
the auditd service has write permissions, even if
someone might add additional hardening options to
the systemd service in the future.

Directory permission bits were copied from the
systemd tmpfiles config for the log directory, and
`make_audit_run_dir()` for the runtime directory.
With RuntimeDirectory/LogsDirectory set,
there is no need to an explicit tmpfiles rule anymore.
@LordGrimmauld
Copy link
Contributor Author

We might also want to set LogsDirectoryMode / RuntimeDirectoryMode

Done. I copied directory permission bits from the systemd tmpfiles config for the log directory, and make_audit_run_dir() for the runtime directory.

@stevegrubb
Copy link
Contributor

We're taking a break from the audit project. We'll look at this when we're back.

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.

2 participants