From unknown Fri Apr 17 00:42:36 2026
X-Loop: owner@bugs.x2go.org
Subject: Bug#1156: [X2Go-Dev] SSH daemon could not be started
Reply-To: Mihai Moldovan <ionic@ionic.de>, 1156@bugs.x2go.org
Resent-From: Mihai Moldovan <ionic@ionic.de>
Resent-To: x2go-dev@lists.x2go.org
Resent-CC: X2Go Developers <x2go-dev@lists.x2go.org>
X-Loop: owner@bugs.x2go.org
Resent-Date: Thu, 15 Feb 2018 03:00:02 +0000
Resent-Message-ID: <handler.1156.B1156.151866337827268@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 1156
X-X2Go-PR-Package: x2goclient
X-X2Go-PR-Keywords: 
Received: via spool by 1156-submit@bugs.x2go.org id=B1156.151866337827268
          (code B ref 1156); Thu, 15 Feb 2018 03:00:02 +0000
Received: (at 1156) by bugs.x2go.org; 15 Feb 2018 02:56:18 +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_40,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,RDNS_NONE autolearn=no autolearn_force=no
	version=3.4.1
Received: from localhost (localhost [127.0.0.1])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 20FA45DAEA
	for <1156@bugs.x2go.org>; Thu, 15 Feb 2018 03:56: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 EPc6VJMS46WG for <1156@bugs.x2go.org>;
	Thu, 15 Feb 2018 03:56:09 +0100 (CET)
Received: from mail.ionic.de (unknown [IPv6:2001:41d0:a:588b:1::2])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 57E335DACF
	for <1156@bugs.x2go.org>; Thu, 15 Feb 2018 03:56:09 +0100 (CET)
Received: from [10.30.44.2] (178.162.222.41.adsl.inet-telecom.org [178.162.222.41])
	by mail.ionic.de (Postfix) with ESMTPSA id E042B4F03A13;
	Thu, 15 Feb 2018 03:56:08 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ionic.de; s=default;
	t=1518663369; bh=qOfRHHo5rgFnNYXd4ah1adABo5RQ3rb0yTrPRXLGWXI=;
	h=Subject:To:References:From:Date:In-Reply-To:From;
	b=g+Vo2ka8255xeTkknX9Qqdn944BDhFL5eLwA5BHGcna+YWPaKeugd2whzh0gpoDoC
	 NQpxQ2j4U48Hk19+koCpoxc4hO319yvyPS9l++o+rVThDcZtkcSWSd9OyPKlpOrGxx
	 0e1r/49fTsLWNFcBhina3M0DThRoOoxj+q5tSzVM=
To: Gromit <gromit8192@gmail.com>, 1156@bugs.x2go.org
References: <ae94a4e0-4b91-8ffe-f582-05bf2b738361@gmail.com>
From: Mihai Moldovan <ionic@ionic.de>
Message-ID: <f2d92818-b527-d9cb-bd8c-915457e33125@ionic.de>
Date: Thu, 15 Feb 2018 03:56:08 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <ae94a4e0-4b91-8ffe-f582-05bf2b738361@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="6vICqj2PLpDHkDIBcWmdbSk6PL9V896V1"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--6vICqj2PLpDHkDIBcWmdbSk6PL9V896V1
Content-Type: multipart/mixed; boundary="whv2HgLtcS192mGGEk0B6pBgWQOJvPrGt";
 protected-headers="v1"
From: Mihai Moldovan <ionic@ionic.de>
To: Gromit <gromit8192@gmail.com>, 1156@bugs.x2go.org
Message-ID: <f2d92818-b527-d9cb-bd8c-915457e33125@ionic.de>
Subject: Re: [X2Go-Dev] SSH daemon could not be started
References: <ae94a4e0-4b91-8ffe-f582-05bf2b738361@gmail.com>
In-Reply-To: <ae94a4e0-4b91-8ffe-f582-05bf2b738361@gmail.com>

--whv2HgLtcS192mGGEk0B6pBgWQOJvPrGt
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

* On 01/29/2018 01:55 PM, Gromit wrote:
> Had this same problem under Windows 10.
>=20
> Started x2goclient.debug --debug and it showed me that the
> permissions for the ssh_host_rsa_key are too open (0770).
>=20
> Installed cygwin to check these permissions under windows and the user-=
=20
> and groupname where the same username. The rights where 700. Somehow th=
e=20
> rights for the group where inherited from the user when they have the=20
> same owner/group-name.
>=20
> Fixed it by changing the group for ssh_host_rsa_key from the username t=
o=20
> 'Users' under cygwin.

Yes, that's very unfortunate. As far as I could find out, that's a known =
bug (or
feature, or whatever) in Cygwin.

Sadly, I have no idea how to fix that without telling users to install ch=
mod,
cygwin bash and fixing permissions manually. That's certainly not the bes=
t way
to deal with that wide-spread issue.



Mihai


--whv2HgLtcS192mGGEk0B6pBgWQOJvPrGt--

--6vICqj2PLpDHkDIBcWmdbSk6PL9V896V1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIzBAEBCgAdFiEEbhHQj3UzgcdE8cg8H9Yu2W4lOocFAlqE9sgACgkQH9Yu2W4l
OodKGhAA3w3f23UWKwB2I60ExulGWFiz8+jxZG+WMh05aoKMCv+E29f7Lq2MbZt5
5eryDkEOAlAJVCePU7PE8t0hk17XahGN2BosMzoLAraxxANt8sBlfO4lG71tbpkH
3bsx38hFXibV3UDcBIOh48F3/nX4dVNv5s4OLMLeNYfRIsvErN/8Xho14HXJJ7Gq
2S84YXUrjHL8mVjlGaW1DPoZNMaau6IhFAnexzzv0U1GapOxRQDZ5mg/TGgWd5vF
fgEdJsQAHvvGyQ2DyvPoX7wPz4/HSAiKpC3S6TglvqHuWdmqwnAdcdS/mWg2qCM5
zxQJ+pHIT+NAvNGK2Uw4RT+kPp11xCgBjseanRO4qE7IWMETGI8xv+RD2lsA10Lb
QiFDjd3gtPD7tRhhB8dm43OH7Mt1Zh6Fq4mkq015nY+/T2H4tCfe7tskzaN0cQ/1
rBjgKBhPubUBQJ0fDWwidbSYPmj7u2luyAtAVwblUZ3nxaqWeSsaAwyUy/BnSSez
V11Bm8uNYg1buBuaGF7rn/GixiFGInUTySQJn3WoeqTMp1BKhVb/tJH+ghmn8KwN
TRtwtgpm/yjEn8WoryJspwJxoUMd9bvqNKRXJTIaLDkC167RSr1hh3L3bCMi2tMI
JA7RjjgOgAvSraYhAwa3xrFTMtVssYF3dKDtXpp6uzw8mSHzX5M=
=G11Z
-----END PGP SIGNATURE-----

--6vICqj2PLpDHkDIBcWmdbSk6PL9V896V1--
