From abo@dsl.dk  Fri Apr 19 10:35:04 2013
Received: (at submit) by bugs.x2go.org; 19 Apr 2013 08:35:05 +0000
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.0 required=5.0 tests=HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE,T_DKIM_INVALID,URIBL_BLOCKED autolearn=ham version=3.3.2
Received: from eu1sys200aog123.obsmtp.com (eu1sys200aog123.obsmtp.com [207.126.144.155])
	by ymir (Postfix) with SMTP id A12EF5DB05
	for <submit@bugs.x2go.org>; Fri, 19 Apr 2013 10:35:04 +0200 (CEST)
Received: from mail-oa0-f72.google.com ([209.85.219.72]) (using TLSv1) by eu1sys200aob123.postini.com ([207.126.147.11]) with SMTP
	ID DSNKUXEBuK8DY79O570xNB+oGDZYKbPgGTGf@postini.com; Fri, 19 Apr 2013 08:35:04 UTC
Received: by mail-oa0-f72.google.com with SMTP id i18so1284480oag.7
        for <submit@bugs.x2go.org>; Fri, 19 Apr 2013 01:35:03 -0700 (PDT)
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=GWHOC8HEugtsoCQYelYXl5dg6k/24wKd3dTEBA+RVl0=;
        b=DGbGnuH1vJbnEXj+FAhC+Nuj3hpCxcBbmPFLRKs9XWClV9ZzemLXKqOfHH7g2iT7fD
         m+TsdO4Wc8SCSQffsXKF7RFFis5Je9/lse5gsuNcmm97DgKY7JhoDHptoqn66G7/yJc+
         Ll+GWt5vjQSbT+NiGnOLO8iT8pbThhKEmEedc=
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=GWHOC8HEugtsoCQYelYXl5dg6k/24wKd3dTEBA+RVl0=;
        b=hEAM493C+Xr5e+o/jgPc9BUiSrWSEmUs1fEuZMUBLfGfkbjCNxN2co2cKbDid+t1zh
         RM1uJk1WQq7TbI+BNwubRyoa/ixb+u+bhPSQGkyxKSAYWm3EHmnNZmuNVbfANcZzn8sl
         xeSwd2nQ8wKo7119yqrrw7xJyRPyNvx6HFoKlzxvEeCcin0BrWJkt2lsBBHSdDiEw64o
         wKqigYeJFmP//0I0QoFKiH2ivRIyNy2Vt0aog0zIGRBmuvosDMt40PTN1YzhdW14jmWx
         LAXpU/IezWjzS9Bqf6DFRMu0Ch/6/oAVZFBU5SnVEpCJUd48FqSJ0yNkCcaIMB42Kfg9
         j6VQ==
X-Received: by 10.182.106.102 with SMTP id gt6mr3154942obb.37.1366360503457;
        Fri, 19 Apr 2013 01:35:03 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.106.102 with SMTP id gt6mr3154931obb.37.1366360503160;
 Fri, 19 Apr 2013 01:35:03 -0700 (PDT)
Received: by 10.182.87.200 with HTTP; Fri, 19 Apr 2013 01:35:03 -0700 (PDT)
Date: Fri, 19 Apr 2013 10:35:03 +0200
Message-ID: <CAFJm-UPTixkQ-qT48JT1RZk62DYwihQcZsCLnNLpseExGbqkzg@mail.gmail.com>
Subject: x2goclient in broker-mode does not allow logout
From: Anders Bruun Olsen <abo@dsl.dk>
To: submit@bugs.x2go.org
Content-Type: multipart/alternative; boundary=e89a8fb1fe346d272e04dab29874
X-Gm-Message-State: ALoCoQmdq1W8gFmlWvziOzqVwrn4YO2AM/XbewqB6lLaVIFgpRo42k/NbpErdJHB32HAvS6h/9txf8h4fu142w46uEO5p6gnTFWL+m/sWoenD2VVs5t8uwX8GflWjlgokjDy12Iel2NsL+Yr7xNyouwsO5xt4cE7SA==

--e89a8fb1fe346d272e04dab29874
Content-Type: text/plain; charset=UTF-8

Package: x2goclient
Version: 4.0.1.0

When you have logged in to a server in broker-mode, there is no way to
de-authenticate from the broker, other than closing x2goclient. This is not
a problem on a normal desktop machine, but on thinclients, it is not really
possible to close x2goclient, other than rebooting/shutting down the
machine. This means that users can't go to a thinclient, login and work,
logout and walk away from the machine to allow a different user to use it,
without rebooting the machine after having logged out. This is not
acceptable behavior for a thinclient setup. I think logging out of an
x2goserver should also trigger a deauthenticate from the broker, as this
mimicks the way x2goclient works when not in broker-mode.

-- 
Anders Bruun Olsen
It-ansvarlig
Det Danske Sprog- og Litteraturselskab
(Society for Danish Language and Literature)

--e89a8fb1fe346d272e04dab29874
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Package: x2goclient<div>Version: 4.0.1.0</div><div><br></d=
iv><div>When you have logged in to a server in broker-mode, there is no way=
 to de-authenticate from the broker, other than closing x2goclient. This is=
 not a problem on a normal desktop machine, but on thinclients, it is not r=
eally possible to close x2goclient, other than rebooting/shutting down the =
machine. This means that users can&#39;t go to a thinclient, login and work=
, logout and walk away from the machine to allow a different user to use it=
, without rebooting the machine after having logged out. This is not accept=
able behavior for a thinclient setup. I think logging out of an x2goserver =
should also trigger a deauthenticate from the broker, as this mimicks the w=
ay x2goclient works when not in broker-mode.<br clear=3D"all">
<div><br></div>-- <br>Anders Bruun Olsen<br>It-ansvarlig<br>Det Danske Spro=
g- og Litteraturselskab<br>(Society for Danish Language and Literature)<br>
</div></div>

--e89a8fb1fe346d272e04dab29874--