kdesu dolphin as root not possible [SOLVED-again]

[fedeliallalinea]

[proteusx]

@natrix
Please post your complete build log.

@fedeliallalinea
The patches I posted will fail unless the portage patches have been applied first.

[PrSo]

Sorry for interrupting, and thank you proteusx for those patches.

On my system I had to make some modification of posted patches since offsets in dolphin's and kate's "main.cpp" files does not match.

Here it goes:

dolphin without modification of "root enable" warning:

[wrc1944]

FWIW, the /etc/portage/patches/kde-apps/kate/kate-18.04-root.patch works fine here.
Applies OK for me:

[natrix]

PrSo: the patch to Kate work fine!

proteusx and PrSo:
A very useful contribution.
Thank you!!

[jhon987]

What about a patch for kwrie-18.18?

[proteusx]

kwrite-18-root.patch

[jhon987]

[nordicruler]

Any working patch for dolphin-18.12.2?

[proteusx]

[nordicruler]

[proteusx]

Here is the dolphin patch I use.

[Hu]

The exit path is triggered by the presence of the environment variable informing it that you are using it insecurely. Rather than continue patching every version, if you insist on overriding the security check, do so by creating a wrapper shell script that runs as root, removes those environment variables, then executes Dolphin.

[nordicruler]

Still not working with this patch

[proteusx]

I cannot reproduce your problem.
Here the start of my build log.

[nordicruler]

[asturm]

kate/kwrite do not need any patching, nor be run with kdesu for editing root owned files. kauth is used to gain write permission when such files are saved.

[jhon987]

kwrite-19.04.3 has now hit Gentoo's stable branch,
the difference in the main.cpp file (from the patch perspecitve) is that instead of starting at line 42:

[asturm]

kate/kwrite can write root owned files just fine without kdesu. Please just give it a try.

[proteusx]

Updated kwrite patch:

[asturm]

You start it as user.

[jhon987]

Thanks @proteusx, once again you're saving the day!

@asturm, oh I have given it enough tries, thank you very much sir. But when I buy a PC and install software I choose on it, I prefer they would serve me instead of me serving them.
I understand there's a potential security (though not very likely) risk in using tools as root, however I don't think that the right way to mitigate it is by disallowing run as root altogether.

You know, that solution reminds me of the time I used to serve in the army, one time a soldier who crossed the road at night from base to reach the bus station at the other side, was ran over to death by a car. So what did the high command decided to do about it? in order to cover their asses they decided to issue a command that soldiers aren't allowed to cross that road at all. So now in order to get to the north of the country, a soldier must have traveled a few hours south first until he reaches a station where a bus north could be reached.

These kind of solutions, are in me view, absolutely ridicules. it's akin to throwing the baby with the bath water - just because you might have a malicious/sloppy program that could potentially take advantage of the root privileges therefore what did the developers decided to do? throw the risk (the bath water) away and at same time prevent the user from using tools (the baby) as root.

It's highly bothersome for me when some directories of mine are (understandably) possible to be accessed only with root credentials and doing it via GUI is much quicker than via command line, and so it's highly bothersome to do that via command line, as well as, when I use root dolphin to access a folder (that requires root privileges) I then need to open a non-root dolphin in order to open a file that's in there using kwrite, since the polkit prompt is only invoked via non-root user, which means I cannot do it via GUI but only via the command line - which is bothersome, annoying and totally goes against the purpose of having machines to make our lives easier.

I know it's not your fault (I believe its that KDE's martin grablin dude), but since you asked me to try...

[dalek]

jhon987,

I feel pretty much the same way. What I did, I started using a different file manager. I actually have a couple different ones installed that I can use or fall back on if needed. Dolphin isn't the only tool. I like Konqueror but think it died. That said, I think it also disabled being used as root as well.

If you want to avoid this sort of thing, just find a different tool for the job and use that. I use Krusader and it works fine, even has split views as a default. I also have PCmanFM and friends installed as well. Just find one those doesn't subscribe to the thought that making things hard for you is the only way to keep you safe. As I've posted before, maintaining a Gentoo install without root access is pretty much impossible. There is almost always some config file that has to be edited or something and generally, that requires root.

Hope that gives you some other options if you are interested. If not today, you may be later on.
_________________
My rig: Gigabyte GA-970A-UD3P mobo, AMD FX-8350 Eight-Core CPU, ZALMAN CNPS10X Performa CPU cooler,
G.SKILL 32GB DDR3 PC3 12800 Memory Nvidia GTX-650 video card LG W2253 Monitor
60TBs of hard drive space using LVM
Cooler Master HAF-932 Case

[wrc1944]

I'm more concerned with dolphin. The only way I can get it working as root now after the great proteusx patches are broken once again is to place this alias in /root/.bashrc.

[Blind_Sniper]

I've just updated dolphin and kate without any problem and can run them as root without any aliases and exportes, just using "kdesu dolphin"
I have no idea what's wrong with patches (I do not use any patches), but building dolphin manually works still just fine:
1.