From: muradm <mail@muradm.net>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: control@debbugs.gnu.org, 56971@debbugs.gnu.org
Subject: bug#56971: greeter user permissions are not enough to talk with seatd
Date: Thu, 04 Aug 2022 15:52:32 +0300 [thread overview]
Message-ID: <874jys2m01.fsf@muradm.net> (raw)
In-Reply-To: <b5687a1a3eebc0cce2564634bc4e191cf7abd931.camel@ist.tugraz.at>
[-- Attachment #1: Type: text/plain, Size: 2452 bytes --]
Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> writes:
> block 56971 by 56690 56699
> thanks
>
> Hi muradm,
Hi Liliana,
> Am Donnerstag, dem 04.08.2022 um 12:45 +0300 schrieb muradm:
>> [...] greeter (e.g. gtkgreet) requiring communication
>> with seatd is failing to start, causing "black screen"
>> behavior on active terminal (switching to the other non seatd
>> related terminal is possible, for manual permissions
>> adjustment as workaround).
>>
>> To address this issue, we need more flexible control over
>> seatd user/group, which creates seatd.sock, and greeter user
>> which connects to seatd.sock.
> Okay.
>
>> However, not all greeters require that, so I decided to make
>> more flexible.
> Flexibility for its own sake is not always the right solution.
> On the
> other hand, looking at the two patches, it appears they are to
> be used
> in combination?
>
No, technically they are not strongly dependent on each other,
could be applied one after another in no particular order.
After both are applied, in cooperation they address this issue.
>> Propsed solutions consists of:
>>
>> * 56690 - gnu: seatd-service-type: Should use seat group.
>> With this change, if seatd-service-type is present in the
>> system configuration, "seat" group will be added, and seatd
>> will run as root/seat. Group is configurable, but default is
>> "seat".
> Why just the group and no user? Is it not possible to launch
> seatd as
> non-root?
seatd provides a way for display servers to access input/output
devices
without having to be root. So seatd it self has to run as root.
When seatd opening socket as root/seat, all members of seat would
be able to communicate with it. Also socket could be opened with
seat/seat for instance, but there is no specific point in doing
so.
Will be one more unused system user around.
Arch seems to follow similar way, root/seat is ok for socket.
Also will signal that seatd is running as root.
>> * 56699 - gnu: greetd-service-type: Add greeter-extra-groups
>> config field.
>> With this change, if user wants to use seatd-service-type with
>> greeter requiring seatd.sock, he can add "seat" group to
>> greeter-extra-groups field.
> Note that you still have a TODO on that patch.
That TODO is from the initial commit, it is about cgroup file
system mounting, and totally out of scope of this issue.
> Cheers
Thanks in advance
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-08-04 13:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 9:45 bug#56971: greeter user permissions are not enough to talk with seatd muradm
2022-08-04 11:08 ` Liliana Marie Prikler
2022-08-04 12:52 ` muradm [this message]
2022-08-05 6:11 ` Liliana Marie Prikler
2022-08-05 6:48 ` muradm
2022-08-05 8:04 ` Liliana Marie Prikler
2022-08-07 20:48 ` muradm
2022-08-08 5:54 ` Liliana Marie Prikler
2022-08-26 17:06 ` bug#56690: " Liliana Marie Prikler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874jys2m01.fsf@muradm.net \
--to=mail@muradm.net \
--cc=56971@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=liliana.prikler@ist.tugraz.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.