X2Go Bug report logs - #290
SSH key based authentication problems

Full log

Message #25 received at 290@bugs.x2go.org (full text, mbox, reply):

Received: (at 290) by bugs.x2go.org; 13 Apr 2014 13:51:36 +0000
From mikedep333@gmail.com  Sun Apr 13 15:51:36 2014
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,FREEMAIL_FROM,
	T_DKIM_INVALID autolearn=ham version=3.3.2
Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 031755DA79
	for <290@bugs.x2go.org>; Sun, 13 Apr 2014 15:51:35 +0200 (CEST)
Received: by mail-wi0-f182.google.com with SMTP id d1so2937993wiv.9
        for <290@bugs.x2go.org>; Sun, 13 Apr 2014 06:51:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=KyfWtA46MMzrShPSMN8wu6UnbO5wmqOSD++J9h7eRs4=;
        b=z0p1c1D8bprf6bC51qSppfavDkKfouAuLkOsGUCnBPx+vQsTRVTgIFOuaTg9i0F7bN
         6DXGSvqlJMWGeeXZAhe13kpXwPb0BxTHjT0yRGN4JEmgdxdf209Bm8ZSWYPDMPTpS8o8
         CYZii/JU3gk5xmqlLXRqN3bH7wLn0hw0IvxCtUkhU99gNid9X44nWGjuNzUffJmcoMhB
         3tVqDVMQFOKN3l0QfGnpZb7reVOur7yBWaz4h5VaFjbKjdZHnnTWgYa0W3GY0ASLhXGO
         p5vXynLL1YvvKzjNJUyDJnZhiDL7GI8PaLS7SRJplX6OgpszC/8MqokOtr0YcCA7RfuK
         Mvng==
MIME-Version: 1.0
X-Received: by 10.194.5.5 with SMTP id o5mr28666851wjo.16.1397397095668; Sun,
 13 Apr 2014 06:51:35 -0700 (PDT)
Received: by 10.180.12.236 with HTTP; Sun, 13 Apr 2014 06:51:35 -0700 (PDT)
Date: Sun, 13 Apr 2014 09:51:35 -0400
Message-ID: <CAMKht8h2n5=Fu-iFGu09aOAZfJa4bAzCfageniSGKM-D39heOg@mail.gmail.com>
Subject: Workaround with PuTTYGen
From: Michael DePaulo <mikedep333@gmail.com>
To: 290@bugs.x2go.org
Content-Type: text/plain; charset=ISO-8859-1

1st of all, as the Windows maintainer for X2Go Client, I intend to
either add support for using PuTTY private keys, or at least update
X2Go Client to give a meaningful error message about PuTTY private
keys not being supported.  I currently have no ETA on when I will
implement this.

2nd, if Pageant support is not working for you in x2goclient 4.0.1.3
or 4.0.1.3+build2, upgrade to x2goclient 4.0.2.0. This is bug 448.

3rd, as Stefan briefly mentioned, With PuTTYGen (0.63), a workaround
is available. Basically you are just exporting your private key from
PuTTY format to OpenSSH format. This workaround is the intended design
of PuTTY suite. Here are full instructions.

Step 4 isn't required, but I strongly encourage you to follow it. Step
5 only applies to if you wish to use cygwin.

1. Generate or load your putty private key with PuTTYGen
2. Select Conversions -> export OpenSSH key
3. Save the private key file to a file. I strongly encourage you to
save it with the standard openSSH filename. The standard filename
would be, depending upon what type of key your generated,:
id_rsa
id_dsa
4. Copy the "Public key for pasting into OpenSSH authorized_keys file"
into a new file in your favorite text editor; notepad will suffice.
Save it as one of the standard filenames in the same folder:
id_rsa.pub
id_dsa.pub
When saving it, make sure you do not put .txt on the end of the filename!
5. If you have cygwin installed on your Windows client, copy or move
both files to: ~/.ssh/ . Create ~/.ssh/ if it does not exist. Make
sure you set the correct permissions though:
chmod 700 ~/.ssh && chmod 600 ~/.ssh/*
6. Configure your X2Go Client to use your id_rsa or id_dsa file.

Send a report that this bug log contains spam.