On Sat, Sep 5, 2015 at 4:52 AM, Tom H <[log in to unmask]> wrote:
> On Thu, Aug 27, 2015 at 12:29 PM, Nico Kadel-Garcia <[log in to unmask]> wrote:
>> On Thu, Aug 27, 2015 at 9:08 AM, Tom H <[log in to unmask]> wrote:
>>> On Mon, Aug 24, 2015 at 6:54 PM, ToddAndMargo <[log in to unmask]> wrote:
>>>>
>>>> I can run anything as a regular user but not my apps
>>>> as root. I am sure a reboot will fix this, but
>>>> is there a way to fix this without rebooting?
>>>>
>>>> This started after I fired up two VM's in KVM
>>>>
>>>> # leafpad smb.conf &
>>>> [1] 16905
>>>> [root@localhost samba]# No protocol specified
>>>> leafpad: Cannot open display:
>>>>
>>>> # echo $DISPLAY
>>>> :0.0
>>>
>>> You need to specify XAUTHORITY=
>>
>> Doing a "sudo" or "su" to run things as the root user can also clear
>> your individual user X settings, as can using ssh to access the local
>> system as a root user if you do not allow X forwarding.
>>
>> Personally, I tend to run as a user, then "ssh -l root localhost" with
>> my SSH settings and keys set to permit my SSH user on localhost to
>> connect with ssh-agent and X11 forwarding enabled.
>
> systemd introduced "machinectl shell localhost" in systemd 225 that
> essentially does the same as "ssh localhost" from an env perspective.
>
> Since it's being rebased to 219 for SL 7.2, perhaps that command'll be
> included in SL 7.4 with a systemd 22x (or it might be backported at
> some point...).

systemd's tendency to find a particular issue with a known, stable
toolkit and then bolt it onto systemd is scaring the tar out of me.
Attempting to replace su or sudo seems to be yet another example of
this. The subject has been discussed, heatedly, in the Fedora mailing
list.

I'm afraid that su replacement looks like a Linux-only major security
problem begging to happen.