please improve remote accessibility from Linux

[eudoxos]

I would very much like to use MSYS2 remotely (read: sitting at my regular Linux workstation, ssh'ing to MSYS2 for windows-specific things since msys2 does not even install under Wine currently) and there are 3 things which would be of a great help:

• official (packaged, debugged and so on) sshd setup, listening on different network ports for different subsystems (mingw64, mingw32, plain msys, others...) and setting environment variables (such as $PATH) appropriately for each of them, similarly to separate launchers in the windows menu (there are several howtos floating around, which work with smaller or bigger tweaks and frustrations); including sudo (for administrator access in terminal) would be a cheery on the top;
• packaging basic x11 utils (such as xauth) so that ssh -X works;
• enabling xcb (x11) backends for major toolkits (Gdk, Qt) so that GUI apps can be run remotely.

Feel free to close the issue if deemed out of question.

[1480c1]

This might be better suited for MSYS2-packages since this primarily relate to packages inside there (although ssh is the only package I think mentioned other than gdk and qt that we actually package)

[1480c1]

I personally wish x11 was packaged with either msys2 or mingw-w64, so I don't have to use vcxsrv and I might be able to try the whole x11+pulseaudio thing

[Biswa96]

How about packaging vcxsrv in mingw-packages? This always rings in my head

the main focus of MSYS2 is to provide a build environment for native Windows software and the Cygwin-using parts are kept at a minimum.

[jeremyd2019]

sshd configs would be possible. I wonder if simply configuring sshd to allow the client to set MSYSTEM environment variable would work well... Then you could add AcceptEnv MSYSTEM to sshd_config, and something like this in client ~/.ssh/config:

Host xxx-mingw32
    HostName xxx
    SetEnv MSYSTEM=MINGW32
Host xxx-mingw64
    HostName xxx
    SetEnv MSYSTEM=MINGW64
...

[eudoxos]

sshd configs would be possible. I wonder if simply configuring sshd to allow the client to set MSYSTEM environment variable would work well...

I just tried and it seems to work very nicely. Thanks for the tip!