https://bugs.kde.org/show_bug.cgi?id=387974
--- Comment #10 from Andrius Štikonas <andr...@stikonas.eu> --- (In reply to David from comment #9) > (In reply to Andrius Štikonas from comment #8) > > Why would we allow running dolphin as root. We are trying to prevent user > > from even starting a single GUI application running as root. And here the > > suggestion is to use the whole session as root. That's much worse security > > wise than single GUI app. > > As for why: for example, when you need to modify permissions of files and > folders, copy/delete files in certain directories, edit system stuff, among > others. > > By restricting users to launch Dolphin as root, you are not making people > more secure. You are just annoying people by making their workflow less > convenient and forcing them to use a different application to do the job, > such as Nautilus or Pluma. > > Consider that one of the reasons why some people use KDE and its apps in the > first place is because they are sick from other DE's attitude of thinking > they know better than their users how they should do stuff. By the way, it wasn't me who disabled running Dolphin as root, it was Martin Flösser but I think he would object to a patch like this. All of these tasks could be done with Polkit. Copying/deleting files with KAuth is almost done in KIO. Kate already supports editing system file with KAuth, you just open file in Kate, edit it, and when you save it, you are asked for password. Changing permissions sound like a fairly simple KAuth helper. I know form the developers perspective it's simpler not to use KAuth. Martin was telling me since maybe two years ago not to use root for KDE Partition Manager. And as you can imagine Partition Manager really needs root for almost every single thing it supports, no other GUI app in KDE needs root in so many places. Yet over the last year I with some help from other people were porting it to use KAuth and we are getting close. -- You are receiving this mail because: You are watching all bug changes.
