Hi Mike,
Having setup a thinclient environment with x2gothinclient the bug we were talking about during our development sprint in march, where a dialog box appears, asking for a passphrase for a key, when being auto-logged-in over a broker. Pressing cancel allows me to be logged in anyway. We suspected it might be the way my machine is setup, but on the newly created thinclient-environment I now have, it also happens. Only on this setup, pressing cancel does not help. The dialog box just reappears. This means that currently, our thinclients can't login using a broker with auto-login. Any idea how to debug this problem?
-- Anders Bruun Olsen It-ansvarlig Det Danske Sprog- og Litteraturselskab (Society for Danish Language and Literature)
Hi Anders,
On Do 18 Apr 2013 15:56:51 CEST Anders Bruun Olsen wrote:
Hi Mike,
Having setup a thinclient environment with x2gothinclient the bug we were talking about during our development sprint in march, where a dialog box appears, asking for a passphrase for a key, when being auto-logged-in over a broker. Pressing cancel allows me to be logged in anyway. We suspected it might be the way my machine is setup, but on the newly created thinclient-environment I now have, it also happens. Only on this setup, pressing cancel does not help. The dialog box just reappears. This means that currently, our thinclients can't login using a broker with auto-login. Any idea how to debug this problem?
I will cross-check with Alex first (he might know a solution) and then
(if not) take a closer look at the x2goclient 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.xf...
I have a guess as to the possible reason for the behavior of the thinclient: the filesystem is of course read-only (nfs-shared root), so no generated ssh private key, needed for the autologin, can be placed there. If this is indeed the reason, then the fact that it just shows a passphrase dialog box is very confusing and this behaviour should be changed. Although my guess could be entirely wrong.
2013/4/18 Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
Hi Anders,
On Do 18 Apr 2013 15:56:51 CEST Anders Bruun Olsen wrote:
Hi Mike,
Having setup a thinclient environment with x2gothinclient the bug we were talking about during our development sprint in march, where a dialog box appears, asking for a passphrase for a key, when being auto-logged-in over a broker. Pressing cancel allows me to be logged in anyway. We suspected it might be the way my machine is setup, but on the newly created thinclient-environment I now have, it also happens. Only on this setup, pressing cancel does not help. The dialog box just reappears. This means that currently, our thinclients can't login using a broker with auto-login. Any idea how to debug this problem?
I will cross-check with Alex first (he might know a solution) and then (if not) take a closer look at the x2goclient 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<mike.gabriel@das-netzwerkteam.de>, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.**de/freebusy/m.gabriel%40das-** netzwerkteam.de.xfb<https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb>
-- Anders Bruun Olsen It-ansvarlig Det Danske Sprog- og Litteraturselskab (Society for Danish Language and Literature)
Hi Anders, On Do 18 Apr 2013 16:16:05 CEST Anders Bruun Olsen wrote:
I have a guess as to the possible reason for the behavior of the thinclient: the filesystem is of course read-only (nfs-shared root), so no generated ssh private key, needed for the autologin, can be placed there. If this is indeed the reason, then the fact that it just shows a passphrase dialog box is very confusing and this behaviour should be changed. Although my guess could be entirely wrong.
AFAIK X2Go Client does not store temp private keys on the file system
(any more) since the migration to libssh2.
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.xf...
-
Anders Bruun Olsen -
Mike Gabriel