I don't think the same ssh-key format that putty uses works anywhere else.
Maybe if you setup the ssh-key using the pseudo-native Win10 ssh-keygen and append that over to the remote system?
Honestly, I haven't used x2go from Windows in over a year. We didn't move to Win10 here. We kept a few systems on Win7 for emergencies and all the others moved to Linux desktops. Not everyone can do that.
Let me look for x2go issues with ssh-keys from Windows10.
Got it working. Use the ssh-keygen program included with x2go, not the putty one.
A quick search found this guide from the x2go team:
https://wiki.x2go.org/doku.php/wiki:...sswordless-ssh
- Ok, so I booted a Win7 box, installed the "current" x2go client.
- Created an ssh-keygen -t ed25519 (using the ssh-keygen in the X2Go-Client directory) and forced it into the directory I wanted/expected. For me, that was d:/Users/thefu/.ssh/ 2 files are created ... id_ed25519 and id_ed25519.pub.
- The .pub file has to be transferred to the remote system. I used the x2go pscp.exe program to do that. On Unix, I'd use ssh-copy-id and it would do the right thing correctly, always.
- From Windows, we are in the 1990s and have to manually get the .pub file over to the remote system,
Now move to the Linux server
- Next append it to the ~/.ssh/authorized_keys file correctly. If you don't already have any ~/.ssh/authorized_keys file, just copy the .pub file into that file/location. Each key must be on 1 line. Some editors insert line breaks rather than wrapping. Don't allow that.
- The permissions need to be 600 on that file and 700 on the ~/.ssh/ directory. Get those wrong and ssh won't work. Security matters.
Back on the client/Windows system,
- run the x2go-client program.
- In the session settings, there's a place to browse to the d:/Users/thefu/.ssh/id_ed25519 file and
- 1 checkbox that says to use that automatically.
The first time you use it, ssh-agent will ask if you want to remember the key-unlock credentials. Your choice. Then for the next few hours, you won't be asked to unlock that ssh key on any system where you've pushed that .pub keyfile.
Personal Notes/Techniques: I use a different key for each customer and for different security levels for systems. For normal servers inside a customer's LAN, I use 1 key. But for any internet facing systems, I use a different key. This sounds like a hassle, but it isn't. On Unix systems, we can specify which keys are used for each remote system in the ~/.ssh/config file - it supports all sorts of other configuration options to make life easier. But that's a different question.
If you don't use ed25519 keys ... well, please go read this:
https://nbeguier.medium.com/a-real-w...s-b26b0b31bfd9 RSA and DSA really shouldn't be used.
I use x2go mainly when traveling, not when I'm at home working. 99.9% of the time, I use straight ssh connections from home. On the LAN, I'll use
ssh -X for X/Windows tunneling. It is much more convenient for me than wasting a full Linux desktop, but we are all different. Right now, I have 22 windows open on my workstation across a few different virtual desktops. Of those, 10 are ssh sessions into other systems inside a terminal each. Each terminal gets started with something like this command:
Code:
xterm -geometry 80x25+1030+50 $XTERM_OPTS -e ssh -X istar &
They have different placement and different remote system names for a nice layout. Some people use
tmux or
screen tools to accomplish the same thing. In the olden days, connectivity was not so great and a disconnect would kill remote programs. I've been lucky - never had that issue. Part of me wishes I'd have learned to use tmux.
You can tune x2go connection parameters as needed. I usually set the connection speed to be 1 less than whatever the truth is. Also, I tweak the image compression to use 4k-png. This is the difference between a nice, fast, experience and something sluggish ... like VNC or RDP.
Anyway, hope this is helpful and I'll see the night vs day difference that x2go provides. xfce is a good choice, btw. Really just avoiding Gnome3 seems to be the only DE requirement for x2go to work well. I've used it from different continents and been happy. I've connected to my Mom's Lubuntu desktop over the slowest DSL possible - basically ISDN speeds. That wasn't snappy, but it was serviceable.
Bookmarks