X2Go Bug report logs - #75
fails to use RSA SSH keys

Toggle useless messages

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

From: Reinhard Tartler <siretart@gmail.com>

To: submit@bugs.x2go.org

Subject: fails to use RSA SSH keys

Date: Thu, 6 Dec 2012 09:11:51 +0100

Package: pyhoca-gui
Version: 0.2.0.4-0~789~precise1

The configuration dialogue asks for a private RSA/DSA keys.
Unfortunately, when I try to use my RSA SSH key, the connection fails
with "not a valid DSA key". Which is correct, but not helpful.

BTW, when browsing for a keyfile, the window title of the file browser
says (in german) "select public SSH Key". I guess it still wants a
private one instead.

-- 
regards,
    Reinhard

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

From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

To: Reinhard Tartler <siretart@gmail.com>, 75@bugs.x2go.org

Subject: Re: [X2Go-Dev] Bug#75: fails to use RSA SSH keys

Date: Thu, 06 Dec 2012 09:48:43 +0100

[Message part 1 (text/plain, inline)]

Hi Reinhard,

On Do 06 Dez 2012 09:11:51 CET Reinhard Tartler wrote:

> Package: pyhoca-gui
> Version: 0.2.0.4-0~789~precise1
>
> The configuration dialogue asks for a private RSA/DSA keys.
> Unfortunately, when I try to use my RSA SSH key, the connection fails
> with "not a valid DSA key". Which is correct, but not helpful.
>
> BTW, when browsing for a keyfile, the window title of the file browser
> says (in german) "select public SSH Key". I guess it still wants a
> private one instead.

I have also observed this behaviour. My main SSH key is an RSA key and  
it works fine.

So problem 1 is the error message: it says DSA (hard-coded) but it can  
mean RSA/DSA.

The ,,not a valid DSA key'' refers to a local private SSH key that  
does not get accepted by the server (no matter if the key locally is  
RSA or DSA).

What is the exact SSH configuration in the sessions file? Do you use  
detction of default key names in the config?

Greets,
Mike






-- 

DAS-NETZWERKTEAM
mike gabriel, rothenstein 5, 24214 neudorf-bornstein
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

[Message part 2 (application/pgp-signature, inline)]

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

From: Reinhard Tartler <siretart@gmail.com>

To: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

Cc: 75@bugs.x2go.org

Subject: Re: [X2Go-Dev] Bug#75: fails to use RSA SSH keys

Date: Thu, 6 Dec 2012 09:53:32 +0100

On Thu, Dec 6, 2012 at 9:48 AM, Mike Gabriel
<mike.gabriel@das-netzwerkteam.de> wrote:
> Hi Reinhard,
>
>
> On Do 06 Dez 2012 09:11:51 CET Reinhard Tartler wrote:
>
>> Package: pyhoca-gui
>> Version: 0.2.0.4-0~789~precise1
>>
>> The configuration dialogue asks for a private RSA/DSA keys.
>> Unfortunately, when I try to use my RSA SSH key, the connection fails
>> with "not a valid DSA key". Which is correct, but not helpful.
>>
>> BTW, when browsing for a keyfile, the window title of the file browser
>> says (in german) "select public SSH Key". I guess it still wants a
>> private one instead.
>
>
> I have also observed this behaviour. My main SSH key is an RSA key and it
> works fine.

That sentence does not make sense to me. Can you confirm that RSA keys
do not work or not?

>
> So problem 1 is the error message: it says DSA (hard-coded) but it can mean
> RSA/DSA.
>
> The ,,not a valid DSA key'' refers to a local private SSH key that does not
> get accepted by the server (no matter if the key locally is RSA or DSA).

Well, this means that the error message then is both wrong and not helpful.

> What is the exact SSH configuration in the sessions file? Do you use
> detction of default key names in the config?

This is my the relevant part of my ~/.x2goclient/sessions file

[20121202161237781818]
iconvfrom = UTF-8
height = 600
speed = 2
setsessiontitle = 0
sessiontitle =
layout = us
width = 800
krblogin = 0
soundsystem = pulse
autostart = 0
type = pc105/us
sndport = 4713
sshproxyuser =
usekbd = 1
autologin = 0
sound = 1
rootless = 0
sshproxyhost =
name = <REMOVED FOR PRIVACY>
iconvto = UTF-8
directrdp = 0
sshport = 22
startsoundsystem = 0
pack = 16m-jpeg
defsndport = 1
useiconv = 0
multidisp = 0
export = ";"
fullscreen = 0
useexports = 0
quality = 9
xdmcpserver = localhost
xinerama = 0
rdpoptions = -u X2GO_USER -p X2GO_PASSWORD
print = 0
usesshproxy = 0
sshproxytunnel = :1::1
variant = altgr-intl
sshproxykeyfile =
fstunnel = 1
applications = TERMINAL, WWWBROWSER, MAILCLIENT, OFFICE
host = <REMOVED FOR PRIVACY>
mimeboxextensions =
user = tartler
key =
directrdpsettings =
icon = /usr/share/icons/PyHoca/128x128/pyhoca-session.png
mimeboxaction = OPEN
rdpport = 3389
rdpserver =
soundtunnel = 1
rdpclient = rdesktop
command = KDE
dpi = 96
published = 0
setdpi = 0
usemimebox = 0



-- 
regards,
    Reinhard

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

From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

To: Reinhard Tartler <siretart@gmail.com>

Cc: 75@bugs.x2go.org

Subject: Re: [X2Go-Dev] Bug#75: fails to use RSA SSH keys

Date: Thu, 06 Dec 2012 10:04:55 +0100

[Message part 1 (text/plain, inline)]

Hi Reinhard,

On Do 06 Dez 2012 09:53:32 CET Reinhard Tartler wrote:

> On Thu, Dec 6, 2012 at 9:48 AM, Mike Gabriel

>> I have also observed this behaviour. My main SSH key is an RSA key and it
>> works fine.
>
> That sentence does not make sense to me. Can you confirm that RSA keys
> do not work or not?

My RSA key here works fine with PyHoca-GUI. So, I think I can confirm  
that RSA keys generally work.

>>
>> So problem 1 is the error message: it says DSA (hard-coded) but it can mean
>> RSA/DSA.
>>
>> The ,,not a valid DSA key'' refers to a local private SSH key that does not
>> get accepted by the server (no matter if the key locally is RSA or DSA).
>
> Well, this means that the error message then is both wrong and not helpful.

Yes, ACK. Will address that later with a commit.

>> What is the exact SSH configuration in the sessions file? Do you use
>> detction of default key names in the config?
>
> This is my the relevant part of my ~/.x2goclient/sessions file
>
> [20121202161237781818]
> iconvfrom = UTF-8
> height = 600
> speed = 2
> setsessiontitle = 0
> sessiontitle =
> layout = us
> width = 800
> krblogin = 0
> soundsystem = pulse
> autostart = 0
> type = pc105/us
> sndport = 4713
> sshproxyuser =
> usekbd = 1
> autologin = 0
> sound = 1
> rootless = 0
> sshproxyhost =
> name = <REMOVED FOR PRIVACY>
> iconvto = UTF-8
> directrdp = 0
> sshport = 22
> startsoundsystem = 0
> pack = 16m-jpeg
> defsndport = 1
> useiconv = 0
> multidisp = 0
> export = ";"
> fullscreen = 0
> useexports = 0
> quality = 9
> xdmcpserver = localhost
> xinerama = 0
> rdpoptions = -u X2GO_USER -p X2GO_PASSWORD
> print = 0
> usesshproxy = 0
> sshproxytunnel = :1::1
> variant = altgr-intl
> sshproxykeyfile =
> fstunnel = 1
> applications = TERMINAL, WWWBROWSER, MAILCLIENT, OFFICE
> host = <REMOVED FOR PRIVACY>
> mimeboxextensions =
> user = tartler
> key =
> directrdpsettings =
> icon = /usr/share/icons/PyHoca/128x128/pyhoca-session.png
> mimeboxaction = OPEN
> rdpport = 3389
> rdpserver =
> soundtunnel = 1
> rdpclient = rdesktop
> command = KDE
> dpi = 96
> published = 0
> setdpi = 0
> usemimebox = 0

Ah... your are still using 0.2.0.4 of pyhoca-gui (and probably  
0.2.0.10 of python-x2go?).

Can you please try 0.2.1.0 of pyhoca-gui + python-x2go and report back  
if the problem persists (before I dig into old code...).

Greets,
Mike




-- 

DAS-NETZWERKTEAM
mike gabriel, rothenstein 5, 24214 neudorf-bornstein
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

[Message part 2 (application/pgp-signature, inline)]

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

From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

To: 75@bugs.x2go.org

Cc: 75-submitter@bugs.x2go.org, control@bugs.x2go.org

Subject: Resolved in PyHoca-GUI 0.2.1.1 (with Python X2Go 0.2.1.1 and Python Paramiko 1.9.0)

Date: Thu, 20 Dec 2012 10:20:08 +0100

[Message part 1 (text/plain, inline)]

close #75
thanks

Hi Reinhard,

I have checked this issue on my machine.

This bug used to exist for quite a while and I ignored it.

Reproducing with old pyhoca-gui versions:

  o generate two rsa/dsa pub+priv keypairs A and B
  o install the pubkey of A on the server
  o test that privkey of A for authentication -> works
  o test privkey B for authentication -> fails with ,,not a valid DSA key''

The error message is raised in Python Paramiko.

With latest pyhoca-gui code the issue has vanished. If you use an  
invalid key (i.e. one that fails to auth with the server), then  
pyhoca-gui falls back to password authentication.

Feel free to reopen this bug, if you experience this differently with  
versions >= 0.2.1.1 of Python X2Go and PyHoca-GUI.

Greets,
Mike

-- 

DAS-NETZWERKTEAM
mike gabriel, rothenstein 5, 24214 neudorf-bornstein
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

[Message part 2 (application/pgp-signature, inline)]

Send a report that this bug log contains spam.