Add systemd unit to setup application scope and add hardening. #27325
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
That's perhaps not worse than being placed in the cgroup from the application the launches tdesktop given that mime-apps-spec implementations usually don't create a cgroup. I'd rather encourage people to switch to dbus-broker if that's something important to them, instead of maintaining a unit file as a part of tdesktop. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
After enabling support for D-Bus activation 2dfe858 application may started by the dbus service.
In this case application is placed into the incorrect cgroup scope inherited from dbus service.
This change provides systemd user unit for application to put application to the applications scope. Also, add some hardening to prevent unnecessary permissions.