PolicyKit + KDE

John Tapsell johnflux at gmail.com
Thu Sep 3 13:28:08 BST 2009

2009/9/3 Thiago Macieira <thiago at kde.org>:
> Em Quinta-feira 03 Setembro 2009, às 09:45:14, você escreveu:
>> 2009/9/3 Aaron J. Seigo <aseigo at kde.org>:
>> > On September 2, 2009, John Tapsell wrote:
>> >> running "kdesu kill PID".  The PolicyKit 'problem' sorta takes
>> >> ksysguard back a step, in that before ksysguard could reliably kill a
>> >> root process but now it can't without someone manually copying policy
>> >> files around.
>> >
>> > and takes it a step forward by letting the system (or sys admin) let
>> > certain users do so without having access to root or access to other root
>> > privileges.
>> Sure, it adds functionality, but it also takes away functionality in
>> that if KDE is installed in some network mapped /opt  drive, say, then
>> ksysguard cannot kill root own processes.
> It's a system admin problem.
> The kdesu helper programs still need to be setuid root to do anything. And if
> you run from NFS, the default is to do root squashing.

It does?  I thought it just ran sudo, which would probably be
installed on a non-root squashed partition.  kdesu relies on some KDE
program being setuid?


More information about the kde-core-devel mailing list