DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=W/ezDEMVKJjLednR
	/wG6izg4vEcydCDjiwP6ammA/M6XIcoslWqjXDChg0pZqrojo1O++wpXY7VYJ9yg
	t10O0/iC5XZAQdyc4R6BIOEI1kI/pkx2tYkmahed5u1IWS/+a94kZGsNabgApgYQ
	EcBEEvmRl3eY4kGxcNTL2T7hFao=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: installing sshd | Win 10 1909 build
To: cygwin@cygwin.com
References: <79ab161a-5e1d-e6b2-f46c-275ce7dd719b@gmail.com> <1934397243.20191227000253@yandex.ru> <f5667cf6-8a2d-c282-a974-be4aca30cb92@gmail.com> <9f8f05c4-2a03-7fef-0e76-207b53273acb@gmail.com> <e13fec5f-ee92-f1c0-ae2f-5abe261857d7@gmail.com>
From: Marco Atzeri <marco.atzeri@gmail.com>
Message-ID: <4442b520-b723-4f9e-e29d-78743db7db52@gmail.com>
Date: Fri, 27 Dec 2019 06:00:31 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1
MIME-Version: 1.0
In-Reply-To: <e13fec5f-ee92-f1c0-ae2f-5abe261857d7@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Am 27.12.2019 um 00:03 schrieb Evan Cooch:
> 
> 
> On 12/26/2019 4:48 PM, Marco Atzeri wrote:
>> Am 26.12.2019 um 22:13 schrieb Evan Cooch:
>>> Thanks, but insufficient. Where is the Cygwin sshd equivalent of the 
>>> following for the Windows 10 implementation of OpenSSH?:
>>>
>>> https://www.pugetsystems.com/labs/hpc/How-To-Use-SSH-Client-and-Server-on-Windows-10-1470/ 
>>>
>>>
>>> Is there an equivalent for Cygwin sshd, that deals in a step-by-step 
>>> fashion specifically with handling recent build of Windows 10, all of 
>>> which have openSSH pre-installed?
>>>
>>
>> Evan,
>> Bottom post on this mailing list, please.
> 
> Sure -- will do moving forward.
> 
>>
>> $ cygcheck -p bin/sshd
>> Found 4 matches for bin/sshd
>> openssh-debuginfo-8.0p1-2 - openssh-debuginfo: Debug info for openssh
>> openssh-debuginfo-8.1p1-1 - openssh-debuginfo: Debug info for openssh
>> openssh-8.0p1-2 - openssh: The OpenSSH server and client programs
>> openssh-8.1p1-1 - openssh: The OpenSSH server and client programs
>>
>> so openssh is the package providing the ssh demon/server
> 
> Presumably on a machine running the cygwin sshd, correct?

no. Option -p asks the cygwin website and the reply provides
all packages and versions. For this reason I asked for bin/sshd
to trim the answer only to binary programs

>> $ cygcheck -l openssh | grep config
>> /etc/defaults/etc/sshd_config
>> /etc/defaults/etc/ssh_config
>> /usr/bin/ssh-host-config
>> /usr/bin/ssh-user-config
>> /usr/share/man/man5/sshd_config.5.gz
>> /usr/share/man/man5/ssh_config.5.gz

Option -l is for the current installation

>>
>> ssh-host-config is used to install and configure the Cygwin server
>> ssh-user-config is used to install user specific files.
>> Its use is very simple, step by step approuch as mentioned on
>> /usr/share/doc/Cygwin/openssh.README
>>
>>
>> As you can not have two different sshd demons running
>>  at the same time, use "net start <service>" and
>> "net stop <service>" that are your usual windows command friends.
> 
> OK -- but my question wasn't so much about using openSSH, but rather, 
> how to do an install of Cygwin ssh on a Win 10 machine, which already 
> has a native ssh server client 'bult in'. A number of us have tried 
> using the standard approaches for installing cygwin and having sshd run 
> as a service (approaches that worked fine on Win 7, and pre-1803 builds 
> of WIn 10), but have had problems with Windows complaining (or, if not 
> complaining, not allowing a different sshd). It seems as if you need to 
> 'turn off' or 'uninstall' something with recent Win 10 builds to get 
> Cygwin sshd to install -- and work -- as a service.  That is the step 
> some of us  are hoping someone can step us through.

for what I remenber the collision in installing was caused
by MS calling the service sshd just as Cygwin one.
Now the service is installed as cygsshd so there should be no
collision in installation.
See on
https://www.cygwin.com/ml/cygwin-announce/2019-04/msg00017.html

"* sshd(8) Cygwin: Change service name to cygsshd to avoid collision
    with Microsoft's OpenSSH port."

Of course you can not have the two runnning together
so you neeed to stop or disable the MS one.

For that you can use
C:\Windows\System32\services.msc

or the MS "net" command

Regards
Marco

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