[systemd-devel] Future of Polkit & XML with kdbus

Kay Sievers kay at vrfy.org
Fri Nov 8 20:34:39 PST 2013


On Sat, Nov 9, 2013 at 5:29 AM, Greg KH <gregkh at linuxfoundation.org> wrote:
> On Sat, Nov 09, 2013 at 01:27:46AM +0100, Jason A. Donenfeld wrote:

>> Forgive me in advance if the underlying reasonings behind these
>> questions are a bit naive...
>
> What are those underlying reasonings?
>
>> Will kdbus make use of polkit? If partially so, will it be feasible to
>> have a normal desktop system with systemd+kdbus that does not require
>> polkit? Will polkit play a smaller role going forward? Will it be
>> phased out in any way?
>
> Why?
>
>> Perhaps tangentially related: will kdbus make use of dbus's current
>> xml definition files? Will all that xml somehow be a part of future
>> dbus situations?
>
> Why?
>
>> More generally: can all the not-so-nice stuff go away with the kdbus?
>
> What exactly is "not so nice"?  How are you going to change all of the
> exising dbus users?

It is a bit like asking if a new socket type will replace a web
server. :) So, no, kdbus is a low-level transport to exchange any sort
of data between peers; it has nothing really to do with polkit.

Like everything, things get rewritten/improve over time. If you have
specific problems with polkit, please be more specific, so people can
work in that direction after there is a general agreement what to do.

Polkit solves a real problem, nothing else at the moment even remotely
solves; and kdbus will not change that in any way.

Kay


More information about the systemd-devel mailing list