X2Go Bug report logs - #1253
ssh broker : bad error feedback in interaction mode

version graph

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

Reported by: Walid MOGHRABI <w.moghrabi@servicemagic.eu>

Date: Tue, 13 Feb 2018 18:35:02 UTC

Severity: normal

Found in version 4.1.1.1

Full log


🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#1253: ssh broker : bad error feedback in interaction mode
Reply-To: Walid MOGHRABI <w.moghrabi@servicemagic.eu>, 1253@bugs.x2go.org
Resent-From: Walid MOGHRABI <w.moghrabi@servicemagic.eu>
Resent-To: x2go-dev@lists.x2go.org
Resent-CC: X2Go Developers <x2go-dev@lists.x2go.org>
X-Loop: owner@bugs.x2go.org
Resent-Date: Tue, 13 Feb 2018 18:35:02 +0000
Resent-Message-ID: <handler.1253.B.151854667726602@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: report 1253
X-X2Go-PR-Package: x2gobroker-ssh
X-X2Go-PR-Keywords: 
Received: via spool by submit@bugs.x2go.org id=B.151854667726602
          (code B); Tue, 13 Feb 2018 18:35:02 +0000
Received: (at submit) by bugs.x2go.org; 13 Feb 2018 18:31:17 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.7 required=3.0 tests=BAYES_50,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,URIBL_BLOCKED autolearn=ham autolearn_force=no
	version=3.4.1
Received: from localhost (localhost [127.0.0.1])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 7AFFF5DAEA
	for <submit@bugs.x2go.org>; Tue, 13 Feb 2018 19:31:14 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de
Received: from ymir.das-netzwerkteam.de ([127.0.0.1])
	by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id wzGnudFL0HVI for <submit@bugs.x2go.org>;
	Tue, 13 Feb 2018 19:29:46 +0100 (CET)
Received: from zm-01.servicemagic.eu (zm-01.servicemagic.eu [176.31.236.17])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 75E775DACF
	for <submit@bugs.x2go.org>; Tue, 13 Feb 2018 19:29:46 +0100 (CET)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by zm-01.servicemagic.eu (Postfix) with ESMTP id DA6CF806BB9C4
	for <submit@bugs.x2go.org>; Tue, 13 Feb 2018 19:29:45 +0100 (CET)
DKIM-Filter: OpenDKIM Filter v2.11.0 zm-01.servicemagic.eu DA6CF806BB9C4
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=servicemagic.eu;
	s=frmailing; t=1518546585;
	bh=ZCr4gtFMEeSN6f/OTxRlZ9B+lu635QmQFbLL1WADem0=;
	h=Date:From:To:In-Reply-To:Subject:From;
	b=bikjHtfLF1yN2TnjQD7Xh3D+oXBRv/r+f4zH2xa+N+rjr07OzcpLoY2xwn2N8iKjW
	 C8S8yDdJJi+mWmIAczhnop1MklCBHu1fvuzGfZ8mIdfbQA5wtervkK0golxaf4lWpG
	 mbg8UYMsBA3Q9CeTGhKdaSzEIv04LYJafPeEGTBQ=
X-Amavis-Modified: Mail body modified (using disclaimer) -
	zm-01.servicemagic.eu
X-Virus-Scanned: amavisd-new at servicemagic.eu
Received: from zm-01.servicemagic.eu ([127.0.0.1])
	by localhost (zm-01.servicemagic.eu [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id nyrwdm2OhedS for <submit@bugs.x2go.org>;
	Tue, 13 Feb 2018 19:29:45 +0100 (CET)
Received: from zm-01.servicemagic.eu (localhost.localdomain [127.0.0.1])
	by zm-01.servicemagic.eu (Postfix) with ESMTP id 72EA0803CC7CC
	for <submit@bugs.x2go.org>; Tue, 13 Feb 2018 19:29:45 +0100 (CET)
Date: Tue, 13 Feb 2018 19:29:45 +0100 (CET)
From: Walid MOGHRABI <w.moghrabi@servicemagic.eu>
To: submit@bugs.x2go.org
Message-ID: <1155172713.4629662.1518546585375.JavaMail.root@servicemagic.eu>
In-Reply-To: <1242363712.4618700.1518541999382.JavaMail.root@servicemagic.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Originating-IP: [195.200.167.70]
X-Mailer: Zimbra 7.2.0_GA_2669 (ZimbraWebClient - GC64 (Linux)/7.2.0_GA_2669)
package: x2gobroker-ssh
version: 0.0.4.0-0~972~ubuntu16.04.1
priority: bug

Using the ssh broker is great because it adds the ability for the x2goclient to interact with the auth mechanism such as PAM so that you get notified that you need to renew a password for example.
This is great but it doesn't always work well.

For example, the user don't get the reason why the access is denied.

Here are different tests I made based on the following setup : x2gobroker in ssh mode with local PAM auth based on Samba Winbind/Kerberos.

I tried both situations to compare :
* with the x2goclient in broker-ssh mode
* with a term rying to connect through SSH


1) Account set for password change with temporary password in Active Directory, user type wrong password (neither old or new one)
* with x2goclient: get message "Access denied. Authentication that can continue: publickey,password,keyboard-interactive"
* with term : "Your account has been locked. Please contact your System administrator. Password: "


2) Account set for password change with temporary password in Active Directory, user type good password

* with x2goclient: get a new password form in order to type (and confirm) the new password. Reseting password works and you get logged in to the broker with the sessions list displayed.
However, if you click on the "cancel" button, x2goclient freeze and must be killed, you're not sent back to the login form.
On the other hand, if you change your password and then be logged in, clicking on the session slot fails because this is the old password that is relayed to the session slot and not the new one. When it fails, you get a new login form to enter your password again, if you type the new password there, it works.

* with term: 
    "Password: ******"
    "Password expired.  You must change it now."
    "Enter new password: ******"
    "Enter it again: ******"
If you cancel (ctrl+c), nothing happen and you get back to the prompt.
If you enter the good old password, you're prompted to change it then you're logged in.
If you enter the wrong password, your prompted to retry 2 times then you get this message "Your account has been locked. Please contact your System administrator" (this is our security policy, this is normal behaviour, 2 fauils then blocked for 10mn.


3) Account disabled in Active Directory
* with x2goclient: get message "Access denied. Authentication that can continue: publickey,password,keyboard-interactive"
* with term : "Your account has been locked. Please contact your System administrator. Password: "


Would be great to fix the issues in 2) and would be great to retrieve the error message directly from PAM so that we get the reason.

Regards,
Walid Moghrabi

TRAVAUX.COM
BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403
13591 AIX EN PROVENCE CEDEX 3
---
DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you

Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Sun Jun 16 20:54:16 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.