[policykit-kde-agent-1] [Bug 486453] Show more metadata about the initiating process to help people verify what exactly requested authentication

[Ellie]

https://bugs.kde.org/show_bug.cgi?id=486453

--- Comment #5 from Ellie <el at horse64.org> ---
> Requiring a special key combination to be pressed would be disruptive and annoying Making the dialog system-modal in the style of UAC and GNOME would also be disruptive and annoying, and also and not actually provide any additional security.

The point is doing both actually does provide significant additional security,
unless I am mistaken:

The special key prompt makes sure that it's actually the system or compositor
showing this dialog and not a rogue fullscreen app, and because it's
system-modal you then also know that while it's showing no other app can
somehow get in front and confuse you. It's why Windows UAC offers this mode,
and at least as an option I think it makes sense.

I know it sounds cumbersome, but how else would a rogue app be effectively
prevented from fooling the user here? All information shown in the dialog
including the PIDs is usually available to most processes on the system, so
forging the dialog isn't exactly difficult right now. That seems like it
renders the whole idea of an elevation dialog somewhat moot, however.

-- 
You are receiving this mail because:
You are the assignee for the bug.