Use DynamicUser instead of a static kolibri user #2
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.
As discussed in pull request #1, this removes the static
kolibri
system user, and instead uses systemd'sDynamicUser=
option. That allows us to greatly simplify how this component is implemented.Unfortunately, dbus policy files don't work with dynamic users (systemd/systemd#9503), so the following policy breaks:
At the moment, I am changing the policy to allow any user to own the Kolibri daemon's name on the system bus, but that is not ideal. I think we would need a better solution to that problem before merging this.