X2Go Bug report logs - #141
X2Gobroker: session autologin does not work

version graph

Package: x2goclient; Maintainer for x2goclient is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goclient is src:x2goclient.

Reported by: Anders Bruun Olsen <abo@dsl.dk>

Date: Thu, 7 Mar 2013 10:03:01 UTC

Severity: normal

Tags: pending

Found in version 4.0.0.4

Fixed in version 4.0.1.1

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

Bug is archived. No further changes may be made.

Full log


🔗 View this message in rfc822 format

X-Loop: git-admin@x2go.org
Subject: Bug#141: X2Gobroker: session autologin does not work
Reply-To: Anders Bruun Olsen <abo@dsl.dk>, 141@bugs.x2go.org
Resent-From: Anders Bruun Olsen <abo@dsl.dk>
Resent-To: x2go-dev@lists.berlios.de
Resent-CC: X2Go Developers <x2go-dev@lists.berlios.de>
X-Loop: git-admin@x2go.org
Resent-Date: Thu, 07 Mar 2013 10:03:01 +0000
Resent-Message-ID: <handler.141.B.13626498165765@bugs.x2go.org>
Resent-Sender: git-admin@x2go.org
X-X2Go-PR-Message: report 141
X-X2Go-PR-Package: x2gobroker
X-X2Go-PR-Keywords: 
Received: via spool by submit@bugs.x2go.org id=B.13626498165765
          (code B); Thu, 07 Mar 2013 10:03:01 +0000
Received: (at submit) by bugs.x2go.org; 7 Mar 2013 09:50:16 +0000
Received: from eu1sys200aog116.obsmtp.com (eu1sys200aog116.obsmtp.com [207.126.144.141])
	by ymir (Postfix) with SMTP id 036075DB0D
	for <submit@bugs.x2go.org>; Thu,  7 Mar 2013 10:50:15 +0100 (CET)
Received: from mail-oa0-f72.google.com ([209.85.219.72]) (using TLSv1) by eu1sys200aob116.postini.com ([207.126.147.11]) with SMTP
	ID DSNKUThi1wGbKce1vam8cX7Nr22tJe/lWyEE@postini.com; Thu, 07 Mar 2013 09:50:16 UTC
Received: by mail-oa0-f72.google.com with SMTP id j6so1885995oag.3
        for <submit@bugs.x2go.org>; Thu, 07 Mar 2013 01:50:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=dsl.dk; s=google;
        h=x-received:mime-version:x-received:date:message-id:subject:from:to
         :content-type;
        bh=H0N0ff6qDaP9VKEpDGSDtxE3z9SopwnG6jxGbIYS61I=;
        b=QRIG0t6LWc9KGEYN6tBVbklxaoKAeZwN4Qs9XcD3IzA3Pw/8kyMXhA55nEuy9iz6Zx
         /9J3NcMVOZ1uUQUqlN1IfsD0N3O3/C+p83gswr3e+gfAQryeLIiug/8bw6EMdf/5MrVA
         gThqmXT6AHQnwED9u0cgNnahYGaMRMgo8mNdE=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=x-received:mime-version:x-received:date:message-id:subject:from:to
         :content-type:x-gm-message-state;
        bh=H0N0ff6qDaP9VKEpDGSDtxE3z9SopwnG6jxGbIYS61I=;
        b=k87pHVXSc4/oOZeFNehPSmqZssSStLREfYuMaRqiPbjbZULht8NXCEYzyHeVj2kQsh
         Y04FtcGmjFWOnU076bBTN7Cucgez+YQUXKOD8oMj2IPFw7AWDO0auiGT61esH1l57jZO
         p+/Qa47otNQZpjHCRylYHfWJuqtzF1xUIRXL3WBodtat9ZROfuKBBiY4NlYEieZ6IGlR
         A/++25Jpj2nE/RLOJ2VxSjBs59YJVOOvEYB/FK8upzkb5TDZOwLDykgSRx1Qx6e1KYBr
         MZzwhIgZgddZ1bN6UUHlzTBQU2XOfhVNZc11iwjPECL6rFYQQWxv7zz/Daa1+AIMqJyI
         +v9w==
X-Received: by 10.182.31.109 with SMTP id z13mr25557105obh.37.1362649814752;
        Thu, 07 Mar 2013 01:50:14 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.182.31.109 with SMTP id z13mr25557102obh.37.1362649814559;
 Thu, 07 Mar 2013 01:50:14 -0800 (PST)
Received: by 10.182.95.211 with HTTP; Thu, 7 Mar 2013 01:50:13 -0800 (PST)
Date: Thu, 7 Mar 2013 10:50:13 +0100
Message-ID: <CAFJm-UODjWseVb-r9U-s1tQPHCteeNmsumwepNAcH0i6GVoc2Q@mail.gmail.com>
From: Anders Bruun Olsen <abo@dsl.dk>
To: submit@bugs.x2go.org
Content-Type: multipart/alternative; boundary=14dae93b5c802680de04d752a237
X-Gm-Message-State: ALoCoQlFK56JmVtuO2gk+8TczwLAVuxKCtXW5y2MFNqpt8N0NMhm2tFFJjLsTJZ5z5i4+CFoUxrg+FLEAR0UwNfOmdl5qRkVGs0rtTJJTXVzV+U7SJ0HNibi60sEqBersEn3GFLXF5R7k8g/kr77FpTUWPZgSigWWg==
[Message part 1 (text/plain, inline)]
Package: x2gobroker
Version: 0.0.0.7

When broker-session-autologin=true is set for a profile, a temp
ssh-key-pair is generated. The pubkey is added to %h/.x2go/authorized_keys
on the term-server and the private key is given to x2goclient.
Unfortunately this does not seem to work for us. When we try to login this
way, a dialog box is shown, asking for a "passphrase to decrypt a key".
At first in our test-setup we thought this worked, because I already had
password-less login to the terminal-servers using ssh-keys. As soon as I
move my .ssh dir, this other problem occurs. It also occurs for for users
without any ssh-keys setup. I can see that the pubkey is successfully added
(and removed after 20 seconds) on the term-server in
$HOME/.x2go/authorized_keys. The sshd on the term-server is set to also
look in %h/.x2go/authorized_keys.

-- 
Anders Bruun Olsen
It-ansvarlig
Det Danske Sprog- og Litteraturselskab
(Society for Danish Language and Literature)
[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Tue May 28 20:43:22 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.