From: Roy Bamford <neddyseagoon@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] State of elogind integration and the default +elogind local USE flag on xorg-server.
Date: Fri, 22 Mar 2019 21:09:16 +0000 [thread overview]
Message-ID: <L4NY7PMO.2LU5IZLM.BBJUESBP@DTOKYS3G.4BM7AIUG.PHC5OAEM> (raw)
In-Reply-To: <5aa7ae5e-94d8-2428-ccd5-ea4c04ebf5e4@gentoo.org> (from slashbeast@gentoo.org on Fri Mar 22 20:32:16 2019)
[-- Attachment #1: Type: text/plain, Size: 1867 bytes --]
On 2019.03.22 20:32, Piotr Karbowski wrote:
> Hi,
>
[snip]
> - We should go back to +suid -elogind default.
> - We should actually NOT put suid on Xorg if USE="suid elogind" but
> put
> suid bit with USE="suid -elogind".
> - We should only ever enable elogind in desktop profiles.
>
> Personally I'd like to stay without enabling suid by default on
> xorg-server, as otherwise hardly anyone will ever drop the suid from
> it,
> which would be a big step back. Gentoo tried to drop suid from
> xorg-server a handful of times, let's make the current one a final one
> :)
>
> I'd like to propose doing the following:
>
> - Keywording elogind on missing archs
> - Making elogind a global USE flag
> - Switching desktop profiles to elogind from consolekit while still
> preserving -suid +elogind on xorg-server for those that does not use
> desktop profiles (systemd profiles users not affected)
> - Making pambase always install the configuration for pam_elogind.so,
> the same way it does for pam_gnome_keyring.so at this very moment,
> effectively removing elogind USE flag from it.
>
> What do you all think about?
>
> -- Piotr.
>
This looks broken by default.
[ebuild R ] x11-base/xorg-server-1.20.4:0/1.20.4::gentoo USE="doc glamor ipv6 udev xorg xvfb -debug -dmx (-elogind) -kdrive -libressl -minimal (-selinux) -static-libs -suid* -systemd -unwind -wayland -xcsecurity -xephyr -xnest"
elogind is hard masked and suid is being turned off.
Its arm64, so I expect to find a few rough edges.
However, changes like this need to be coordinated across all arches.
Take a pat on the back for the elogind work and a slap on the wrist
if my arm64 systems don't work any more.
Its still building, I'll test later.
--
Regards,
Roy Bamford
(Neddyseagoon) a member of
elections
gentoo-ops
forum-mods
[-- Attachment #2: Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-03-22 21:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 20:32 [gentoo-dev] State of elogind integration and the default +elogind local USE flag on xorg-server Piotr Karbowski
2019-03-22 20:43 ` Brian Evans
2019-03-22 20:48 ` Piotr Karbowski
2019-03-22 20:47 ` Andreas Sturmlechner
2019-03-22 21:07 ` Piotr Karbowski
2019-03-22 21:13 ` Andreas Sturmlechner
2019-03-22 20:56 ` Andrew Savchenko
2019-03-23 0:20 ` Alexander Tsoy
2019-03-22 21:09 ` Roy Bamford [this message]
2019-03-22 21:17 ` Michał Górny
2019-03-22 23:30 ` Piotr Karbowski
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=L4NY7PMO.2LU5IZLM.BBJUESBP@DTOKYS3G.4BM7AIUG.PHC5OAEM \
--to=neddyseagoon@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox