[SOLVED] Plasma 5: Executing Kate as root is not possible? Eric, you are kidding, right?

gmgf · 12-19-2017, 06:10 PM

Quote:

Originally Posted by LuckyCyborg

By absolute power I mean that me, as root, to have ability to use any resource (or program) of the operating system, even that results in its complete and unrecoverable damage. An absolute king of the OS.

When you partially deny those rights, the root become a kind of user with administration rights, just like in Windows.

Maybe it would be good to explain your theory to kde developers.

Darth Vader · 12-19-2017, 06:15 PM

You know what? What he says is what happened on Slackware since its inception, 25 years ago.

The root was the "absolute king" in Slackware, even in the latest stable release.

Drakeo · 12-19-2017, 06:18 PM

Careless what others build and push. If you do not like their build. vim main.cpp.
All this over editing the main.cpp. Just set to user 9999. opensource for a reason.

Code:

mkdir build
cd build 
cmake .. 
make 
make install

life is good

The first thing I install is geany. great for developing.

Darth Vader · 12-19-2017, 06:36 PM

Quote:

Originally Posted by Drakeo

Careless what others build and push. If you do not like their build. vim main.cpp.
All this over editing the main.cpp. Just set to user 9999. opensource for a reason.

Code:

mkdir build
cd build 
cmake .. 
make 
make install

life is good

The first thing I install is geany. great for developing.

That works well, specially if you have time to play those games. BUT some uses the OS to work.

And you know what is funny for things like this?

Code:

#ifndef Q_OS_WIN
    // Check whether we are running as root
    if (getuid() == 0) {
        std::cout << "Executing Dolphin as root is not possible." << std::endl;
        return EXIT_FAILURE;
    }
#endif

You can create thousand other users, with exactly root-alike rights, and this little crap will say nothing to them and Dolphin, Kate and Kwrite will run happily in a full access environment.

I should report the bug?

dugan · 12-19-2017, 06:37 PM

Quote:

Originally Posted by Darth Vader

You have a Plasma 5 variant for grownups, please

Grownups don't run X as root.

gmgf · 12-19-2017, 06:43 PM

Quote:

Originally Posted by Darth Vader

You know what? What he says is what happened on Slackware since its inception, 25 years ago.

The root was the "absolute king" in Slackware, even in the latest stable release.

I use kwrite since kde1, so.....

LuckyCyborg · 12-19-2017, 06:50 PM

Quote:

Originally Posted by dugan

Grownups don't run X as root.

Excuse me and my ignorance, but looks like that story has nothing to do with X, but rather, from what I read in the last hour, it is all about Wayland, which has no security concepts at all.

If you open an Wayland display and compositor as root, any Wayland client, with any user can connect to.

Darth Vader · 12-19-2017, 07:14 PM

They have a kind of security policies in Wayland as a compositor plugin, it is called WSM https://github.com/mupuf/libwsm

BUT, the WSM is rather something like the Android policies, though...

Definitively, not a thing for a multi-user environment like the usual suspect Linux distribution, but for embedded devices market.

In fact even Wayland was made as a very lightweight X alternative for embedded devices.

Teufel · 12-19-2017, 08:33 PM

Quote:

Originally Posted by Richard Cranium

Just as a guess, kate is a KDE application while vi and emacs are not.

Why they didn't block root access to konsole?

Richard Cranium · 12-19-2017, 09:55 PM

Quote:

Originally Posted by Alien Bob

I think now you are the one who's insulting me. But hey, I know your posting history and remember you insulted the complete Slackware team for supposedly violating the GPL.
I can understand the logic behind browsing the filesystem as root, since that is basically not touching the filesystem and potentially creates better insight.
On the other hand, instructing me to apply a patch so you can use an effing graphical text editor as root, is bullshit. If you want to edit texts as root, use effing elvis.
Now, eff off.

You seem annoyed.

Richard Cranium · 12-19-2017, 09:56 PM

Quote:

Originally Posted by Teufel

Why they didn't block root access to konsole?

How would they do that? Tell us.

Richard Cranium · 12-19-2017, 10:00 PM

Quote:

Originally Posted by dugan

Grownups don't run X as root.

Code:

$ ps -ef | grep X
root      2872  2860  3 Dec12 tty7     06:45:38 /usr/libexec/Xorg -br -novtswitch -quiet :0 vt7 -nolisten tcp -auth /var/run/xauth/A:0-DLtouc

Uh-oh.

Teufel · 12-20-2017, 12:32 AM

Quote:

Originally Posted by Richard Cranium

How would they do that? Tell us.

By adding a snippet of code like this:

Code:

#ifndef Q_OS_WIN
    /**
     * Check whether we are running as root
     **/
    if (getuid() == 0) {
        std::cout << "Executing Kate as root is not possible. To edit files as root use:" << std::endl;
        std::cout << "SUDO_EDITOR=kate sudoedit <file>" << std::endl;
        return 0;
    }
#endif

to main.cpp from "kde-apps/konsole" package

solarfields · 12-20-2017, 12:46 AM

Quote:

Also, I am contemplating removing the dolphin patch just to piss you off.

that's the spirit. You show 'em AlienBob!

Darth Vader · 12-20-2017, 02:08 AM

Quote:

Originally Posted by Teufel

Why they didn't block root access to konsole?

Quote:

Originally Posted by Teufel

By adding a snippet of code like this:

Code:

#ifndef Q_OS_WIN
    /**
     * Check whether we are running as root
     **/
    if (getuid() == 0) {
        std::cout << "Executing Kate as root is not possible. To edit files as root use:" << std::endl;
        std::cout << "SUDO_EDITOR=kate sudoedit <file>" << std::endl;
        return 0;
    }
#endif

to main.cpp from "kde-apps/konsole" package

Because the Konsole developer happens to be another person, who figured out already that the Linux and BSD permissions are GROUP based, in a nutshell?

There is no such thing as USER EINZ in Linux (or BSD), but any member of the group "root" (and/or "wheel" in some implementations) has elevated access permissions, then go figure how much efficient is this code snippet.

Finally, to understand the epic fail of their approach at whole, imagine that while KWrite and Kate has access denied for root, the KDevelop works well, while it is basically a Kate in steroids with tons of extensions for developing, including abilities of scripting and executing even (remote) console commands.