X-Recipient: archive-cygwin@delorie.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:references :mime-version:content-type:in-reply-to; q=dns; s=default; b=rEun W+CtTXWJpONOMnxrMDmYrajggPIRutzDjHMyud0fSmFFZyzX7bY6YEGxwQC5PBmQ edgcqzokgsikI9ycL+JRUf3zL5KXeKxU/WqNhjGUkSawi/7hyyYv/oAUS+8GClYR PBatRZ3CnllPhaj6/qDz2OL2LrJlXKNo6xaapbI= 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:references :mime-version:content-type:in-reply-to; s=default; bh=mdr+wKzM7T V2mzkpRvQu1QxfGxU=; b=s2cEArP7T46j1us6n8DgSshMimwRiu9+I1Pn48xEOI V3b0fNEc0QDcf7XvB9XjF/oAstcEZUxa2xlEG6fd067ic7aFxfYrOr+w8mJZa6m6 qTQ+Mw4OrfNK64eqVFKY84pp5oQNC8sn8aTdaTImsgoUzs3u3fl2k7MNpkG5ZW3H 0= Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.4 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT autolearn=no version=3.3.2 spammy=201903, H*RU:sk:mail.sa, Hx-spam-relays-external:sk:mail.sa, HX-HELO:sk:mail.sa X-HELO: mail.santannapisa.it Received-SPF: none receiver=ucs.santannapisa.it; client-ip=80.116.124.90; envelope-from=forenr@lyx.org Date: Tue, 19 Feb 2019 11:30:44 +0100 From: Enrico Forestieri To: cygwin@cygwin.com Subject: Re: Problem with sshd on W7 with 32bit cygwin 3.0 Message-ID: <20190219103044.GA919@GIOVE> References: <20190218105842.GA1050@GIOVE> <20190218141111.GZ4256@calimero.vinschen.de> <20190218160402.GA1319@GIOVE> <20190218205450.GI4256@calimero.vinschen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190218205450.GI4256@calimero.vinschen.de> User-Agent: Mutt/1.11.2 (2019-01-07) On Mon, Feb 18, 2019 at 09:54:50PM +0100, Corinna Vinschen wrote: > On Feb 18 17:04, Enrico Forestieri wrote: > > On Mon, Feb 18, 2019@03:11:11PM +0100, Corinna Vinschen wrote: > > > > > > Two workarounds for now: > > > > > > - Start sshd as 64 bit Cygwin process. > > > - Utilize https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd3 > > > > Thank you. The second method above worked. This is a private network, > > so that is Ok. > > I uploaded new developer snapshots with fixes for this problem: > https://cygwin.com/snapshots/ Please give it a try. Thanks. I can confirm that with this snaspshot sshd works fine without the need for the workaround. -- 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