X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 9687138930DB
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1592675244;
	bh=JP9BvNzTU7F4wdqcRA+HKfzoALP9E1+MwO4XYHkdDrw=;
	h=References:In-Reply-To:Date:Subject:To:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	From;
	b=pAamg+NyLJFhvGuEd5WVryc7WBkpNf2KjRW7jSLCUsvhi4smbE5xp4UC7sD1S0ZgX
	1Q3NO3kbN/uD0km7+HuGq0BU9h0YXTGPOWzUmJ+yXN8Z+XnRYXxZ+txIvzCCgnjMNv
	XUuzXFIL16SG/nJryawDmUa04H4VN5ix3N5w+ACU=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 26105383E827
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:cc;
	bh=G/Gw0NayTy+/FzViQn3RcxPXnSM6JSCz4egIm1cywwQ=;
	b=QawyQ01FPTBghVjx7rNhCsAhTV3LcEbHli8TqsRnrHFpPLZUN39eUu8t16cSIGS7SI
	yD0ddgW5ovxEGphpHFllnsX/F2pfL8L4MVjbge5fQmqVppxeVcDSrEvLu21qtfTPzP9g
	sayCgVG7IXTL+zjzP342RB00ORP0N6EGxVcHAVvch3iIcBlh9vwADxAIDgbLhQGkOc3H
	0OoQnPyRL1w7WwozRnZo1a9VVAmjItDtNIr8ZV0qiGkkY7wcaPAGeaCckXfJXgYHAzHD
	aIf7qJ+8iCZHoIAY+GQ+5vM4bIJZn0lGl1uk2WKDCbWpmzgkZmwZDEfIMUrnCwu8HwqH
	4Mkg==
X-Gm-Message-State:	AOAM533g4ivvuB/kPuQQ2AatK3pW24fiFLwNM+f9n5fhb5AvXkWfksSO
	kkEWwxuaErk6tnP3ZhF+RYis4tosNLLuy+fNMUZR5xcd
X-Google-Smtp-Source:	ABdhPJxm7WHTiyoMpBYztg7fgKAvCwqeyWgosVNDVSSAy+8K1sqIGWk1FIcdYitY5NYO3z218LIE+qO0gUxQuIIirDs=
X-Received:	by 2002:a92:7414:: with SMTP id p20mr9881871ilc.77.1592675241663;
	Sat, 20 Jun 2020 10:47:21 -0700 (PDT)
MIME-Version:	1.0
References:	<CADF5XCynm6M2+teNKBDOeR_u0vT5pmbdctXrThdseR_FZz=5HA AT mail DOT gmail DOT com>
	<c3e72b9b-3c20-6502-b23d-c8258446108a AT gmail DOT com>
In-Reply-To:	<c3e72b9b-3c20-6502-b23d-c8258446108a@gmail.com>
Date:	Sat, 20 Jun 2020 13:46:45 -0400
Message-ID:	<CADF5XCzDvyR=mi_kLfwMWXCr=Uzhz=z96tBmRYvEc6r4XEN+NA@mail.gmail.com>
Subject:	Re: ssh troubles
To:	Marco Atzeri <marco DOT atzeri AT gmail DOT com>
X-Spam-Status:	No, score=-4.0 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, HTML_MESSAGE,
	RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-Content-Filtered-By:	Mailman/MimeDel 2.1.29
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<http://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Raman Gupta via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Raman Gupta <rocketraman AT gmail DOT com>
Cc:	cygwin AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

On Wed, Jun 17, 2020 at 4:21 PM Marco Atzeri via Cygwin <cygwin AT cygwin DOT com>
wrote:

> On 17.06.2020 20:46, Raman Gupta via Cygwin wrote:
> > Hello all, for some reason I've started having troubles with cygwin sshd,
> > despite having successfully used it for years. Not sure if some recent
> > Windows updates broke it or something, but now I'm getting the infamous:
> >
> > sshd: PID 1855: fatal: seteuid 1049703: No such device or address
> >
> > I believe I've followed all the advice given on this list over the years
> > regarding this error:
> >
> > * installed cygwin 64-bit (this fixed it for a while, but now its broken
> > again)
> > * uninstalled the service, and reinstalled with ssh-host-config
> > * verified all permissions on home, .ssh, and authorized_keys files are
> > correct (and configuring in non-strict mode doesn't work either anyway)
> > * running the service as Local System (as installed by recent versions of
> > ssh-host-config)
> > * updated to the latest openssh version available (this also fixed it
> for a
> > while, but then it broke again)
> > * removing any /etc/password or /etc/group files
> > * removing any value for CYGWIN environment variable
> >
> > $ cygcheck -c openssh
> > Cygwin Package Information
> > Package              Version        Status
> > openssh              8.3p1-1        OK
> >
> > What's very odd is that, recently, I seem to be able to get it to work
> with
> > various approaches (see above), it works for a while, and then it borks
> > again.
> >
> > Any ideas?
> >
> > Regards,
> > Raman
> > --
>
> Corporate computer with continuous reset of corporate policy ?
> I had such experience in the past.
>
> please provide the cygcheck.out as ATTACHMENT
> see https://cygwin.com/problems.html


It is a Windows domain, but I manage the domain and AFAIK there is no such
policy / reset mechanism.

Oddly enough, a reboot seems to have "fixed" it, at least for now. I wonder
if the previous "fixes" were more about reboots as opposed to actual
configuration changes as well...

If it works fine, and then randomly breaks until a reboot, what might be
the cause of that?

Regards,
Raman
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -