DMARC-Filter:	OpenDMARC Filter v1.4.2 delorie.com 61BIKNoO2538439
Authentication-Results:	delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results:	delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter:	OpenDKIM Filter v2.11.0 delorie.com 61BIKNoO2538439
Authentication-Results:	delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=m7rGI/cE
X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 86CCD4BA23C6
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1770834022;
	bh=Djdyns/B9sCw0hKCXh3RzgSzGXQjlFkm96W2Yql6/fg=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	From;
	b=m7rGI/cE0I/NZTRVRVJqs6HatlnqHva7eG8W2quz5G83r31WrCHXXB8kKraE/8OW3
	L3ErV4WwXiE/S6O0ATkUInK3+baoo7M9TtYnue733X3g+JugOX69abgekAs6rVOTfN
	hKSGTx9gEC53bg3GSsPVzWhMz6n34p+RUl67HdNM=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.2 sourceware.org 328AA4BA2E15
ARC-Filter:	OpenARC Filter v1.0.0 sourceware.org 328AA4BA2E15
ARC-Seal:	i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1770834003; cv=none;
	b=YfNNa2Swz3JcCrlT9uOt0IWgIlT0zqHr+FeI9deFx1AL0WeLTfRp9gXngmfenBa8nVIT6FEQAJyyaGZ83skFt9veFmRzPeBRo6+OlBdPXXfpjB6muubaSmF2/mDT6c/O0C5HD1D6H+6RZR+uMDgvSxZmTtcDKXzoeIPn7B2x3gE=
ARC-Message-Signature:	i=1; a=rsa-sha256; d=sourceware.org; s=key;
	t=1770834003; c=relaxed/simple;
	bh=Agmve9gQDPr/mfFqJqM6GLnwjExO22gOvTIDNAc4iUk=;
	h=DKIM-Signature:Date:From:Message-ID:To:Subject:MIME-Version;
	b=ZKaMiSk701myCdo8vG+RmwepUuwzqTSX8EtVox+X9rmFqqSwl5H6Mjr9j+OncI/hUdBigLkvlfyYPMwsBswJl4wM13mwCL7ri8/eFmf72EYzrVJShLWkM2yS5al4hN2p8/ELIBj5v8/Y4fJDEd8dfVGbix7aIErcfOKgronNDHI=
ARC-Authentication-Results:	i=1; server2.sourceware.org
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 328AA4BA2E15
X-Yandex-Fwd:	1
Date:	Wed, 11 Feb 2026 21:07:20 +0300
X-Mailer:	The Bat! (v11.4.3) Home
Message-ID:	<632092166.20260211210720@yandex.ru>
To:	Simon Matthews <simon DOT matthews AT bluepearlsoftware DOT com>, cygwin AT cygwin DOT com
Subject:	Re: Second sshd service (32 bit vs 64 bit)
In-Reply-To:	<2bb582c0-26e4-40e0-8612-49275dd06ba4@bluepearlsoftware.com>
References:	<2bb582c0-26e4-40e0-8612-49275dd06ba4 AT bluepearlsoftware DOT com>
MIME-Version:	1.0
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.30
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>
From:	Andrey Repin via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	cygwin AT cygwin DOT com
Cc:	Andrey Repin <anrdaemon AT yandex DOT ru>
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>

Greetings, Simon Matthews!

> Because of historical reasons, I have a number of Windows virtual
> machines with 32-bit cygwin installed, including the cygwin sshd service.

> It appears to be impossible to start a 64-bit bash session from a 32-bit
> session. However, it there is a way to do this, the rest of the post is
> not relevant.

There's a way, you can tell sshd to use a custom binary as a special service,
and start about anything that way.
Probably you'd need a simple wrapper to bridge the gap between the worlds, but
that should be easy,

> During the transition to 64-bit cygwin, I would like to start a 64-bit
> sshd service on a second port (2222, perhaps). When the transition is
> fully complete, I will remove the 32-bit sshd service.

The current state of 64-bit Cygwin is such that there's hardly any need for
32-bit one, unless you have a VERY specific reason.

I'd suggest to collect your usage information, try your stuff out in a 64-bit
Cygwin, and once it all works up to the expectation, just roll out a switch.


-- 
With best regards,
Andrey Repin
Wednesday, February 11, 2026 21:00:43

Sorry for my terrible english...


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