Attachment 136963 Details for Bug 104792 – [PATCH] service: set User=root so that gio doesn't have to look into /etc/passwd

[patch] [PATCH] service: set User=root so that gio doesn't have to look into /etc/passwd

0001-service-set-User-root-so-that-gio-doesn-t-have-to-lo.patch (text/plain), 1.34 KB, created by Lubomir Rintel on 2018-01-25 16:26:12 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Lubomir Rintel

Created: 2018-01-25 16:26:12 UTC

Size: 1.34 KB

patch

obsolete

>From 0137d61aed3f80c033e57a81c4739ee98f75199b Mon Sep 17 00:00:00 2001
>From: Lubomir Rintel <lkundrak@v3.sk>
>Date: Thu, 25 Jan 2018 17:23:14 +0100
>Subject: [PATCH] service: set User=root so that gio doesn't have to look into
> /etc/passwd
>
>GVfs' libgvfsdbus.so GIo module, when automatically loaded, attempts to
>discover if there's a session D-Bus instance to use. It tries real hard
>to get the socket name it would use -- in absence of XDG_RUNTIME_DIR it
>decides to make it up with user's home directory. When HOME is unset
>too, it just tries to figure it out by looking into /etc/passwd. Which
>upsets SELinux that would better not see us looking into it.
>
>We trigger the load of the GIo modules, by using the GFile API to access
>the the ports in /dev. They're utterly uesless to us, but there doesn't
>seem to be a way to disable their load. Oh well.
>
>For now, let's just ensure HOME is set and the problematic path in glib
>is not taken.
>---
> data/ModemManager.service.in | 1 +
> 1 file changed, 1 insertion(+)
>
>diff --git a/data/ModemManager.service.in b/data/ModemManager.service.in
>index 8ea5a1f6..7e16d4d0 100644
>--- a/data/ModemManager.service.in
>+++ b/data/ModemManager.service.in
>@@ -7,6 +7,7 @@ BusName=org.freedesktop.ModemManager1
> ExecStart=@sbindir@/ModemManager
> StandardError=null
> Restart=on-abort
>+User=root
> 
> [Install]
> WantedBy=multi-user.target
>-- 
>2.14.3
>

Actions: View | Splinter Review

Attachments on bug 104792: 136963

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.