| 1 |
On Fri, 17 Jan 2014 06:56:20 +0200, Samuli Suominen wrote: |
| 2 |
|
| 3 |
> Right, only GDM (the display manager for GNOME) has dropped ConsoleKit |
| 4 |
> support so far, that I know, in versions 3.8 and later |
| 5 |
> So other than GNOME, ConsoleKit is still a go -- thus, compatible with |
| 6 |
> OpenRC based system |
| 7 |
|
| 8 |
I tried USE="-consolekit" but it does not help. |
| 9 |
|
| 10 |
> For KDE it might be something else than dbus-glib that needs a |
| 11 |
> recompile, I'd imagine something like kdelibs or polkit-kde-agent, or |
| 12 |
> both It could be something else too, |
| 13 |
|
| 14 |
This problem has been there for a couple of years, it's reasonable to |
| 15 |
assume that all KDE components have been recompiled several times in that |
| 16 |
period. In fact, both of those were rebuilt by emerge -e dbus dbus-glib. |
| 17 |
|
| 18 |
> but setting the suid bit on |
| 19 |
> dbus-daemon-launch-helper is stupidest idea ever, that *really* allows |
| 20 |
> anyone to gain root |
| 21 |
|
| 22 |
Just to be clear, the SUID bit is set by default, I set the other execute |
| 23 |
bit (o+x). The file already has group execute permissions, but adding my |
| 24 |
user to the messagebus group makes no difference |
| 25 |
|
| 26 |
> However if you run a machine with single user and no open ports on the |
| 27 |
> machine whatsoever, the attack vector is propably very small, but I |
| 28 |
> still wouldn't do it |
| 29 |
|
| 30 |
The alternative is to stop using KDE, since none of the proposed |
| 31 |
solutions, nor anything else I've tried, make any difference. |
| 32 |
|
| 33 |
Edit: Dropping KDE may not make much difference, I still get these |
| 34 |
messages when booting without X. |
| 35 |
|
| 36 |
|
| 37 |
-- |
| 38 |
Neil Bothwick |
| 39 |
|
| 40 |
Why is there an expiration date on sour cream? |
Archives