You have to have an X/Windows server running on the machine you sit behind. That server needs to be sufficiently good to support standard X11. I've only seen commercial X/Servers on MS-Windows work. Honestly, I haven't used MS-Windows for remote X since around 2002, so my knowledge on this is mucho out-of-date.
For my needs, it was easier to install/cheaper a hypervisor like virtualbox into MS-Windows, then run a small Linux VM with a GUI - like the 23MB TinyCore Linux, then use that as the X/Server for remote access into other Unix systems. Since it used the real Linux X/Server, compatibility wasn't an issue. Since it is 23MB in size, it needs very little RAM assigned to the VM and is crazy fast. http://tinycorelinux.net/downloads.html OTOH, TinyCore Linux is a bit odd and not exactly friendly to end users. It is the basis for many specialized devices that have 1 purpose. In this case, you'd use it as an X/Server and only as an X/Server.
The X11Forwarding settings is the default in /etc/ssh/sshd_config on Ubuntu.
MS-Windows implementation of ssh is lacking, BTW. I have no experience trying to get ssh -X working on it. I do know that Putty uses an odd version of ssh-keys, so if that might be the plan, I can't help. I have used PuTTY to remotely start GUI programs after starting a local X/Server. Doing this means it would not use the ssh tunnel AND we have to manually set the DISPLAY environment variably AND we have to open any firewalls to allow the X/Clients to connect the X/Server. Using a proper ssh -X implementation avoids the DISPLAY environment variable - as ssh does that automatically.
The Win10+ ssh implementation doesn't provide the ssh-copy-id tool, which makes ssh-key exchange harder. You'll want to do that manually and be careful like we had to be in the mid-1990s. Copy the public key to the correct file on the remote system and be certain to ensure the file and directory permissions aren't molested. ssh is picky about file permissions. It only took MSFT 20 yrs to make ssh port for MS-Windows. Hopefully, they will take less time to add ssh-copy-id quicker. It is the easiest way to exchange the ssh key from the ssh-client to the ssh-server.
Https://ubuntuforums.org/showthread....6#post13916386 Run 2 commands. That's it - at least on Linux.
I run thunderbird with this exact line:
Code:
TB_OPTS="-no-remote " /usr/bin/ssh -X deneb /usr/bin/firejail $FJ_OPTS /usr/bin/thunderbird $TB_OPTS $@ &
However, I'm a bit of a control freak when it comes to computers and do some security things.
The basic line would be:
Code:
/usr/bin/ssh -X deneb /usr/bin/thunderbird -no-remote $@ &
"deneb" is remote system.
My username is the same on both sides, so it isn't needed.
This is part of a script, so I use the full path to every program for added safety. As /usr/bin/ is in the PATH on both systems, if you trust the PATH being correct (I don't in scripts) AND you don't want to pass any arguments into Thunderbird, then you could use
Code:
ssh -X deneb thunderbird -no-remote &
I almost forgot - Mozilla tries to run their programs locally even when we use ssh, so we have to add the no-remote option.