tag #179 pending fixed #179 4.0.1.1 thanks Hello, X2Go issue #179 (src:x2goclient) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=e3b8739 The issue will most likely be fixed in src:x2goclient (4.0.1.1). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit e3b87397d75a7e246d29c4f94b1368e092f27207 Author: Mike Gabriel <mike.gabriel@das-netzwerkteam.de> Date: Wed Jun 12 13:23:05 2013 +0200 Add cmdline option --broker-autologoff: Enforce re-authentication against X2Go Session Broker after a session has been suspended or terminated. (Fixes: #179). diff --git a/debian/changelog b/debian/changelog index 84daa74..c2dcc38 100644 --- a/debian/changelog +++ b/debian/changelog @@ -20,6 +20,9 @@ x2goclient (4.0.1.1-0~x2go1) UNRELEASED; urgency=low patch was applied. Segfault only occurred if the tray icon was not used. - Show session name in notification bubbles. - Update German translation. + - Add cmdline option --broker-autologoff: Enforce re-authentication against + X2Go Session Broker after a session has been suspended or terminated. + (Fixes: #179). [ Ezra Bühler ] * New upstream version (4.0.1.1):
Processing commands for control@bugs.x2go.org:
tag #179 pending Bug #179 [x2goclient] x2goclient in broker-mode does not allow logout Added tag(s) pending. fixed #179 4.0.1.1 Bug #179 [x2goclient] x2goclient in broker-mode does not allow logout There is no source info for the package 'x2goclient' at version '4.0.1.1' with architecture '' Unable to make a source version for version '4.0.1.1' Marked as fixed in versions 4.0.1.1. thanks Stopping processing here.
Please contact me if you need assistance.
179: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=179 X2Go Bug Tracking System Contact owner@bugs.x2go.org with problems
Hi, Mike.
What do you think about making this behaviour default? Because doing logoff by default seems to be a more secure way (and default settings should be secure) + it doesn't require you to close-and-reopen window if you want to de-authenticate from the broker (and switch to other sessions). I think it would be a good idea, especially if this session broker system is mainly aimed at setups with thin clients (less configuration changes for main use-case).
I personally think that it would be better to de-auth from the broker by default, and then have a commandline option that tells x2goclient to stay authenticated to the broker, when the connection to a server ends.
2013/6/12 Nable 80 <nable.maininbox@googlemail.com>
Hi, Mike.
What do you think about making this behaviour default? Because doing logoff by default seems to be a more secure way (and default settings should be secure) + it doesn't require you to close-and-reopen window if you want to de-authenticate from the broker (and switch to other sessions). I think it would be a good idea, especially if this session broker system is mainly aimed at setups with thin clients (less configuration changes for main use-case).
X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev
-- Anders Bruun Olsen It-ansvarlig Det Danske Sprog- og Litteraturselskab (Society for Danish Language and Literature)
-
Anders Bruun Olsen -
Mike Gabriel -
Nable 80 -
owner＠bugs.x2go.org