From yk+bug+x2go@64.re Tue Feb 13 12:38:39 2018 Received: (at 1156) by bugs.x2go.org; 13 Feb 2018 11:38:49 +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.8 required=3.0 tests=BAYES_50 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 84CD05DAEB for <1156@bugs.x2go.org>; Tue, 13 Feb 2018 12:38:39 +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 zi7Yt-56QI2n for <1156@bugs.x2go.org>; Tue, 13 Feb 2018 12:34:16 +0100 (CET) X-Greylist: delayed 1680 seconds by postgrey-1.35 at ymir.das-netzwerkteam.de; Tue, 13 Feb 2018 12:34:15 CET Received: from slow1-d.mail.gandi.net (slow1-d.mail.gandi.net [217.70.178.86]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id F080A5DACF for <1156@bugs.x2go.org>; Tue, 13 Feb 2018 12:34:15 +0100 (CET) Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [217.70.183.196]) by slow1-d.mail.gandi.net (Postfix) with ESMTP id 64300487AA7 for <1156@bugs.x2go.org>; Tue, 13 Feb 2018 11:50:35 +0100 (CET) X-Originating-IP: 151.80.42.161 Received: from zsxc (pt.64.re [151.80.42.161]) (Authenticated sender: mx@64.re) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id 1E9FD17209C for <1156@bugs.x2go.org>; Tue, 13 Feb 2018 11:50:32 +0100 (CET) Date: Tue, 13 Feb 2018 11:50:31 +0100 From: yk+bug+x2go@64.re To: 1156@bugs.x2go.org Subject: Re: [X2Go-Dev] Bug#1156: SSH daemon could not be started Message-ID: <20180213115031.48f4931a.mx@64.re> In-Reply-To: References: X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Mon, 29 Jan 2018 13:55:07 +0100 Gromit wrote: > Had this same problem under Windows 10. > > Started x2goclient.debug --debug and it showed me that the > permissions for the ssh_host_rsa_key are too open (0770). > > Installed cygwin to check these permissions under windows and the > user- and groupname where the same username. The rights where 700. > Somehow the rights for the group where inherited from the user when > they have the same owner/group-name. > > Fixed it by changing the group for ssh_host_rsa_key from the username > to 'Users' under cygwin. Thanks so much for this workaround! I can confirm that I am experiencing the exact same issue on all the Windows 10 installations at work, and that the workaround is working.