X-Recipient: archive-cygwin AT delorie DOT com
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D0C713857363
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=nexgo.de
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=nexgo.de
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nexgo.de;
 s=vfde-smtpout-mb-15sep; t=1653501085;
 bh=Q61tHXKM4PcVN8QJnP6Xt6lUtNB/G34p+GxQoAKHZO4=;
 h=From:To:Subject:References:Date:In-Reply-To:Message-ID:User-Agent:
 Content-Type:From;
 b=Ucthbqc0ETSPMZJen/GTLKvE3mn8mx2dzKH/ckcAso33WT4htUdnRmwymJIa/Hgsm
 wY+qGjDhzW7e3aFxjJDeYXxx1LWg5ZfvojmNkBIEujqS4JL0A/kJlPy9QHxN8hF1II
 LMaQO4SN1DMxnKfdxLRM6X88Wd5AvmeqgmHGD3L8=
From: Achim Gratz <Stromeko AT nexgo DOT de>
To: cygwin AT cygwin DOT com
Subject: Re: Issue with seteuid and openssh
References: <aebd99eefc4e4c6697a9d2dacd8be275 AT bryanhealth DOT org>
Date: Wed, 25 May 2022 19:51:14 +0200
In-Reply-To: <aebd99eefc4e4c6697a9d2dacd8be275@bryanhealth.org> (Dale Lobb via
 Cygwin's message of "Tue, 24 May 2022 22:15:05 +0000")
Message-ID: <877d694i25.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux)
MIME-Version: 1.0
X-purgate-type: clean
X-purgate: clean
X-purgate-size: 1396
X-purgate-ID: 155817::1653501084-00001899-8DEE8A13/0/0
X-Spam-Status: No, score=-3031.3 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,
 SPF_PASS, TXREP,
 T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
 server2.sourceware.org
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
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: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

Dale Lobb via Cygwin writes:
>   Last night, the server rebooted automatically after windows updates.
> After the reboot, the data gateway was then no longer able to connect
> to the server.  This condition persisted until I was informed of the
> issue this morning and connected to the Windows server using RDP to
> take a look at the issue, at which point the SSH connection suddenly
> started working.  Further tests showed this to be entirely repeatable.
> After rebooting the server, the SSHD daemon does not allow
> connections, neither with password nor public key authorization, until
> someone connects to the server via RDP, at which time the SSH
> connections suddenly starts working again.

Check the dependencies on both the cygserver and sshd service
definitions.  You must start them after the network is up (make them
both depend on tcp_ip and sshd depend on cygserver) or they won't work
correctly.  On domain machines that sometimes still isn't quite enough,
so I've set them to "delayed start" in those instances and that seems to
have fixed it.

Also check that the firewall allows connections through whatever port
you've configured sshd to use.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

-- 
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