From unknown Fri Mar 29 10:40:42 2024 X-Loop: owner@bugs.x2go.org Subject: Bug#566: [X2Go-Dev] Bug#566: X2Go Client for Windows 4.0.2.1 cannot create C:\Users\\ssh\known_hosts file when the local Windows account username has non-Ascii characters Reply-To: "George Trakatelis" , 566@bugs.x2go.org Resent-From: "George Trakatelis" Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Tue, 16 Sep 2014 16:10:01 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 566 X-X2Go-PR-Package: x2goclient X-X2Go-PR-Keywords: Received: via spool by 566-submit@bugs.x2go.org id=B566.141088379111881 (code B ref 566); Tue, 16 Sep 2014 16:10:01 +0000 Received: (at 566) by bugs.x2go.org; 16 Sep 2014 16:09:51 +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.5 required=5.0 tests=BAYES_05,T_DKIM_INVALID autolearn=ham version=3.3.2 Received: from mail-wg0-f42.google.com (mail-wg0-f42.google.com [74.125.82.42]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 716C75DB54 for <566@bugs.x2go.org>; Tue, 16 Sep 2014 18:09:50 +0200 (CEST) Received: by mail-wg0-f42.google.com with SMTP id x12so75421wgg.13 for <566@bugs.x2go.org>; Tue, 16 Sep 2014 09:09:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uom.edu.gr; s=google; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=d3ZmB2iMjAhisBv4zzTrCJq62/QVbxK/5sfQtAKmq4k=; b=a0vl0yLNxKs3Pps6vamgFlz6bsW/wpAK80BMO2H0gEZtI3HVh8aJ51lvVe7eZXxUVS ArJcq9qqWUCCgigZm5cT72djMuJU0B9338Ue/q51xZA4YQsQ/RsvktVBVFVWLDZ+tI0f N+Pzb54+TP2FJ6bha09T291GzwNzy45SY7gZs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :thread-index:content-language; bh=d3ZmB2iMjAhisBv4zzTrCJq62/QVbxK/5sfQtAKmq4k=; b=OHN0LroW0/LxDY2cWl7w3YF0oz/dvBJsYU4HZP2ESw1acWXYkoTqDq3SH4gY6VGIP+ BF49IqNs2vgPYjPXwDWbf3TDxz7ALtUphapJbp1rJdBJfre682J74yJW1AhjSgVvCMAX sLkugQHHRWSvoPzOqus8n1UsEyB0mGGyxm+MCB3/W8MK0+rkTSM9NjXrtVKnBsL1gSvp rFU5Bo396uswb8nHFYZ80YpCfLB2fns4ryFSirbBj7TMkiuhyyvfaPWqgkLWHLyqJK31 iFiYRr7PCWFiVk43HnMeXBohKzhNdS1l48SFfSNVgxo5stXIQp9rXsKgrdQmWo22a8tV y9Vg== X-Gm-Message-State: ALoCoQldvBRT/yHHjK7HpwB/kYITzWwmHNVxQM3U/Q2imQP9DhlE67a4nhXB7DOH1e2Hcb5QIHtp X-Received: by 10.194.143.69 with SMTP id sc5mr43080866wjb.26.1410883790001; Tue, 16 Sep 2014 09:09:50 -0700 (PDT) Received: from HomePC (46-4-59.adsl.cyta.gr. [46.103.4.59]) by mx.google.com with ESMTPSA id wr8sm18888109wjb.20.2014.09.16.09.09.48 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 16 Sep 2014 09:09:49 -0700 (PDT) From: "George Trakatelis" To: <566@bugs.x2go.org> Cc: "'Michael DePaulo'" , References: <000001cfb552$3193a8a0$94baf9e0$@gr> <000001cfc60a$32831de0$978959a0$@gr> <20140901195103.Horde.HOAd34FDzvE7MwwNBCtaAg1@mail.das-netzwerkteam.de> <000001cfca83$2b11d830$81358890$@edu.gr> <20140908085833.Horde.1KVN9LjgQ3GOkz4EX-JZjA1@mail.das-netzwerkteam.de> <000001cfd0a5$a1fe42d0$e5fac870$@edu.gr> <000001cfd172$255b96b0$7012c410$@edu.gr> In-Reply-To: Date: Tue, 16 Sep 2014 19:09:44 +0300 Message-ID: <001701cfd1c8$a200cea0$e6026be0$@edu.gr> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 thread-index: Ac/Rq8RMvgsanIo8SHCHEguVclEW+QAFKkhw Content-Language: el Hi Mike, First of all, patch bug566.test.v2.patch definitely solves the problem = as described in bug #566.=20 I have tried successfully both the release and the debug builds you = uploaded=20 both in Windows 8.1 Pro and Windows 7 Professional SP1 with all the = Microsoft updates installed. Now, with regard to bug #397: > 1st of all, you were talking about a home dir with non-Ascii = characters on the client machine, correct?=20 Yes. > Bug #397 refers to when the user's home folder on the server has = non-Ascii characters.=20 > That is why the bug is filed against x2goserver. > Besides, our "fix" for #397 is not to make homedirs with non-Ascii = characters "work".=20 > Our "fix" is to present a better error message and cleanly abort the = session. I see. > Normally I would say that we should clone this bug (566) for X2Go = Client for Linux.=20 > However, the bug report is already extremely long,=20 > I think we should just file a new one and link to this one. Could you = please file one? I was only testing an analogous to bug #566 situation in Linux. To be honest, I had to get round Ubuntu's policy for POSIX user names by = using usermod.=20 That test revealed that nxproxy (in Ubuntu 14.04) crashes when path = names with non-Ascii characters are used, but is it really a situation that deserves to be filed as a bug?=20 I mean it's common for Windows users to have user names in their native = language. On the other hand, Ubuntu (and I suppose Unix in general) dictates=20 exactly what characters are permitted in a user name. If one by-passes this rule, erroneous program behavior may be observed. Can we call it a bug of the program? I don=E2=80=99t know. You decide! =20 -George