From unknown Tue Apr 28 18:25:26 2026
X-Loop: owner@bugs.x2go.org
Subject: Bug#1235: SSH daemon could not be started
Reply-To: "Feustel, Thomas" <tf@ksh.com>, 1235@bugs.x2go.org
Resent-From: "Feustel, Thomas" <tf@ksh.com>
Resent-To: x2go-dev@lists.x2go.org
Resent-CC: owner@bugs.x2go.org
X-Loop: owner@bugs.x2go.org
Resent-Date: Sat, 27 Jan 2018 13:10:02 +0000
Resent-Message-ID: <handler.1235.B1235.151705849119902@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 1235
X-X2Go-PR-Package: x2go client
X-X2Go-PR-Keywords: 
Received: via spool by 1235-submit@bugs.x2go.org id=B1235.151705849119902
          (code B ref 1235); Sat, 27 Jan 2018 13:10:02 +0000
Received: (at 1235) by bugs.x2go.org; 27 Jan 2018 13:08:11 +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 619585DAEB
	for <1235@bugs.x2go.org>; Sat, 27 Jan 2018 14:08:09 +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 eSMcHM0zS8r3 for <1235@bugs.x2go.org>;
	Sat, 27 Jan 2018 14:08:04 +0100 (CET)
X-Greylist: delayed 333 seconds by postgrey-1.35 at ymir.das-netzwerkteam.de; Sat, 27 Jan 2018 14:08:04 CET
Received: from mail.ksh.com (weidenborn-3.vistec.net [213.216.0.30])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id ADDDE5DA81
	for <1235@bugs.x2go.org>; Sat, 27 Jan 2018 14:08:04 +0100 (CET)
Received: from KSHH5.ksh.local ([fe80::cdd4:8515:4351:5295]) by
 KSHH5.ksh.local ([fe80::cdd4:8515:4351:5295%14]) with mapi id 14.03.0361.001;
 Sat, 27 Jan 2018 14:01:58 +0100
From: "Feustel, Thomas" <tf@ksh.com>
To: "1235@bugs.x2go.org" <1235@bugs.x2go.org>
Thread-Topic: SSH daemon could not be started
Thread-Index: AdOXbxY8/VB4+QCmTfKxRzcY3OaVzw==
Date: Sat, 27 Jan 2018 13:01:57 +0000
Message-ID: <D06DC45236BEB849A21C1DB6946FF51103B60473@KSHH5.ksh.local>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [91.32.30.193]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Das Problem wird auf dem Windows Client dadurch ausgel=F6st, das bei der In=
stallation Host-Keys vom Typ RSA f=FCr den SSH Daemon erzeugt werden. Der S=
erver selbst versucht beim Start einer Client Verbindung aber Host-Keys vom=
 Typ DAS einzulesen.
Diese wurden fr=FCher immer erstellt, so dass bei einem Update das Problem =
nicht existiert.

Zwei L=F6sungen existieren:

a) DSA Host-Keys manuell oder mit einem alten Setup erstellen

b) sshd.config anpassen und auf die neuen Keys bzw. Datei verweisen (nicht =
geteset)


Mit freundlichen Gr=FC=DFen

Thomas Feustel