Eduard Lucena wrote:
> A better solution would be to pop up a dialog stating "This
is being run
> as root and could be dangerous".
This is the best apporach, Why don't take it?
Because the upstream developer thinks even bringing up a dialog as root is
already too big a security risk (even though there's clearly nothing you can
do through the known attack vectors – remote-controlling the UI – with a
simple OK-only dialog) and so decided to print the error only to stdout,
which goes nowhere under kdesu.
Unfortunately, upstream is being very unpragmatic here, both by not allowing
a way to proceed anyway and by the user-unfriendly way the error is being
reported.
Kevin Kofler