Some help with PolicyKit basics

[Michael Biebl]

2009/7/27 David Zeuthen <david at fubar.dk>:
>> this still true if the d-bus daemon is restarted?)
>
> The system bus daemon should _never ever_ be restarted. The guarantee
> that unique system bus names are _never_ recycled is a good reason why
> this is so. I know some distributions still live in some interesting
> reality where they think restarting the system daemon is OK... but
> essentially these guys are wrong and doing so is introducing a security
> hole.

Then D-Bus will never ever be suitable for anything else then
single-user desktop systems where it doesn't matter that much if you
have to reboot the system on package upgrades (which is so windows
like btw).

Serious Linux sysadmin will laugh you in the face if you told them
that they have to reboot their server when dbus is upgraded (e.g. in
case of a security related update, in which case you leave a system
vulnerable).

Applications can be fixed, to reconnect to the system bug, and there
also have been discussions, how to support this within the dbus daemon
itself resp. the dbus libraries.
It's just a tough problem to fix, not something which is inherent by
design of D-Bus.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?