X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:mime-version :content-type; q=dns; s=default; b=x+RUm+m1gAHYAHqGmY1W2syTI6wZ2 Mgcj5FWvXk26fAYXXa8zUvVICzFZs61xe1VEynW60uXW2CVtymxg8tfRB7j/O5bM NcdpW0Z5j31zWDGFMCuz7YDej0PFG31HQZjsANlF7i875Q6h6VitWHLITfNE3lnx 2k5G3S/qDbsPQ8= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:mime-version :content-type; s=default; bh=F8FmWMbcshJ6ZcrGzpZa7OW4C6A=; b=eSD 76KkNqszGp2k66PDrKhJAy7qULQfDF01D8Rd39mz3p9XaNxxK8rSB9y1K2PvvJnE yqZoqk8pP0OYcB+FCKDlJ/TrBZRY/RpBlSqeClFVr7IpOOZ+IN3hICNCSTplZHI6 HK8g0kd1FQ0+w7PHkGau5V6gxdKls/LdqNfTzZgI= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=1.5 required=5.0 tests=BAYES_40,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT autolearn=no version=3.3.2 spammy=sshd, ssh, connect, upgrading X-HELO: mail.santannapisa.it Received-SPF: none receiver=ucs.santannapisa.it; client-ip=80.116.124.90; envelope-from=forenr AT lyx DOT org Date: Mon, 18 Feb 2019 11:58:42 +0100 From: Enrico Forestieri To: cygwin AT cygwin DOT com Subject: Problem with sshd on W7 with 32bit cygwin 3.0 Message-ID: <20190218105842.GA1050@GIOVE> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.11.2 (2019-01-07) After upgrading to cygwin 3.0.0 (32bit version) on W7 64bit, it is not possible to connect using ssh. The returned error is something like "Connection closed by x.x.x.x port 22". I also tried the 2019-02-18 snapshot without success. However, simply downgrading to 2.11.2 fixes the issue. This issue does not seem to affect 64bit cygwin versions on W10. -- Enrico -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple