[X2Go-User] X2Go on submarine control system

[Michael DePaulo]

Windows maintainer here.

1st, FYI, You do need "Try auto login" disabled when using an SSH key
file on the Windows client.

2nd, What version of X2Go Client for Windows are you using? If you are
using the latest version (4.0.3.1-20141214), you can use a debug
build. If you can copy the entire command-line output from the debug
build, great. (A command-line window opens when you launch the debug
build.) Otherwise, at least tell us the last few/several lines before
it fails to connect.
Note that you need to either launch the debug build from the start
menu / desktop shortcut, or from the command-line with the "--debug"
argument passed.

Latest debug build:
http://code.x2go.org/releases/binary-win32/x2goclient/releases/4.0.3.1-20141214/non-default-builds/x2goclient-4.0.3.1-20141214-debug-setup.exe

3rd, in addition to #2, please try using PuTTY (Windows SSH client) to
connect to the machine. You'll need PuTTYgen too.

Full installer:
http://the.earth.li/~sgtatham/putty/latest/x86/putty-0.63-installer.exe

Individual binaries you can just download & run (currently 0.63):
http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe
http://the.earth.li/~sgtatham/putty/latest/x86/puttygen.exe

Launch PuTTYgen and import the SSH key by going to: Conversions ->
Import Key -> select your private key file.
Then "Save Private Key".

Then when you launch PuTTY:
specify the hostname/IP
Specify the port (if you never changed the port, 22 is the default).
Then: Connection -> SSH -> Auth -> specify the "Private key file for
authentication"
Go back to "Session".
For convenience, give the session a name and click "Save".
Now click "Open" (to connect.) If you get an error message, please
tell us what the error message is. If not, enter your username on the
server. (If you get an error message after you enter your username on
the server, please tell us what the error message is.)

-Mike#2

On Mon, Jan 12, 2015 at 4:10 PM, Peter Brodsky
<brodsky at apl.washington.edu> wrote:
> No joy yet.
>
> I generated keys on the linux side:
>> ssh-keygen -t dsa
> Copied the public key to "authorized_keys" in ~/.ssh
> Copied the private key by sneaker-net to the Windows machine.
> There, I specified the latter (key file) in the field "Use RSA/DSA key for
> ssh connection".
>
> Then tried connecting - can't do it (tries quite a while, then times out).
> I did try both with and without the box "Try auto login" checked; doesn't
> work either way.
> Left the last 2 boxes unchecked.
>
> ??
> - Pete
>
>
>
> On 01/12/2015 12:39 PM, Stefan Baur wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Am 12.01.2015 um 21:00 schrieb Peter Brodsky:
>>>>
>>>> X2Go will not work with no authentication at all. However, you
>>>> can use
>>>
>>> a SSH Public/Private Key pair to >authenticate, and assign no
>>> password to the private key. That way, you can automate the login
>>> and make things
>>>>
>>>> work with a simple double-click on the icon.
>>>
>>> OK, indeed it will not work without authentication.
>>>
>>> Would like to try the public/private key route.  I've done this for
>>> ssh agents between linux machines, using ssh-keygen to obtain the
>>> keys. Not clear how to do so w/X2GO client running under Windows.
>>> Can you provide some instructions?
>>
>> If you have access to a Linux machine, just run ssh-keygen there with
>> the usual parameters, copy the private key file over to the Windows
>> machine, and specify it in the session settings (there's a field where
>> you can specify the path to an RSA/DSA key).  On the Linux box, add
>> the public key to the authorized_keys file of the user account you're
>> trying to log in as, and you should be all set.
>>
>> If you want to create your key pair on Windows, you will need to use
>> either ssh-keygen from a cygwin install, or PuttyGen.exe from the
>> PuTTY tool suite - for the latter, you will need to use the "export"
>> function of PuttyGen's GUI to save the private key, as PuTTY's own
>> *.ppk key storage files are incompatible with standard ssh.
[...]