Re: "# systrace -c1000:1000 kate" for privilege escalated editing?

On 2015-12-03, Luke Small wrote: > I want to be able to use systrace for privilege escalation for kompare for > sysmerge diffs and kate. Why isn't systrace able to do this? I can't quite figure out what you're trying to do, but running big GUI programs and libraries with

Re: "# systrace -c1000:1000 kate" for privilege escalated editing?

>I can't quite figure out what you're trying to do, but running big GUI >programs and libraries with root privileges (whether that's from systrace or >doas or sudo or su or whatever) is usually not a good idea. Thinking about it now, I guess if you add root write privileges to writing files, you

Re: "# systrace -c1000:1000 kate" for privilege escalated editing?

2015-12-04 0:10 GMT+01:00 Luke Small : > There must be some sort of kernel lock, because if you su - twice into the > 1000 user, it won't open a x window either! I'm sure there is a > conservative security policy at play, X and switching users requires you to read up on

Re: "# systrace -c1000:1000 kate" for privilege escalated editing?

There must be some sort of kernel lock, because if you su - twice into the 1000 user, it won't open a x window either! I'm sure there is a conservative security policy at play, and maybe writing a script to copy write and doas cp will work, but it also doesn't work if I want to write a program

"# systrace -c1000:1000 kate" for privilege escalated editing?

I want to be able to use systrace for privilege escalation for kompare for sysmerge diffs and kate. Why isn't systrace able to do this? -Luke

Re: "# systrace -c1000:1000 kate" for privilege escalated editing?

03 дек. 2015 г. 4:27 пользователь "Luke Small" написал: > > I want to be able to use systrace for privilege escalation for kompare for > sysmerge diffs and kate. Why isn't systrace able to do this? Because noone wrote a systrace policy for Kate and