I wish things were as easy as they were with X11. Being able to ssh into a box and “export DISPLAY=192.168.0.7:0.0” then start an app and have it show up locally is just magical.

▲

chasil 2 days ago | parent | next [-]

Your X network traffic would be clear text over the network if you did it this way.

Instead, you should "ssh -x" or "ssh -y" to pull the traffic over the ssh encrypted channel.

The -y option should be used with caution; read the docs.

▲

jcelerier 2 days ago | parent | next [-]

> Your X network traffic would be clear text over the network if you did it this way.

that's exactly what I want on my local home network

	▲	chasil 2 days ago \| parent [-]
		You will also need to xhost +(host) which has its own problems.

▲

jrvieira 2 days ago | parent | prev [-]

It's capital -X and -Y

-x disables X11 forwarding.

	▲	chasil 2 days ago \| parent [-]
		Whoops.

▲

pjmlp 2 days ago | parent | prev | next [-]

Yeah, the days of remote displaying unwanted adult content on other computers on university lab for anyone clueless about xhost command, as teenagers do.

▲

supportengineer 3 days ago | parent | prev | next [-]

We had a bright future in the past.

	▲	c-hendricks 2 days ago \| parent \| next [-]
		Something tells me modern remote access tools that use video codecs are much more performant than SSH + X forwarding when dealing with resolutions and desktop effects we use today.
	▲	throwaway328 2 days ago \| parent \| prev [-]
		You mean a kind of "Spectres of Marx", Jacques Derrida, 1993, hauntology type thing?

▲

SbEpUBz2 3 days ago | parent | prev | next [-]

There's waypipe.

▲

dingnuts 2 days ago | parent | prev [-]

This still works if X11 is installed on the remote. I have a remote that runs Wayland locally, and I run Wayland in the client machine as well, but I have X11 installed on the remote and X11 forwarding still works, it just opens the remote application in an XWayland window inside the local Wayland session. No biggie

	▲	theodric 2 days ago \| parent [-]
		For now