public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Evan Cooch <evan.cooch@gmail.com>
To: cygwin@cygwin.com
Subject: Re: installing sshd | Win 10 1909 build
Date: Thu, 26 Dec 2019 23:03:00 -0000	[thread overview]
Message-ID: <f5667cf6-8a2d-c282-a974-be4aca30cb92@gmail.com> (raw)
In-Reply-To: <1934397243.20191227000253@yandex.ru>

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?



On 12/26/2019 4:02 PM, Andrey Repin wrote:
> Greetings, Evan Cooch!
>
>> So, is there a 'tried and true, officially sanctioned' way to get Cygin
>> sshd running as a service under the latest build of Windows 10, if you
>> working with a clean, new install of Windows?
>> Thanks much in advance...
> The only "true and tried" supported way of installing Cygwin's SSHD is the one
> using provided ssh-host-config.
> That assuming you are using an up-to-date installation of Cygwin.
> If you intend to use both Windows and Cygwin SSHD, you'll have to resolve
> TCP ports conflict somehow (which should be expected), otherwide, you may
> simple uninstall Windows one.
>
>


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

  reply	other threads:[~2019-12-26 21:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-26 21:05 Evan Cooch
2019-12-26 21:13 ` Andrey Repin
2019-12-26 23:03   ` Evan Cooch [this message]
2019-12-26 23:53     ` Marco Atzeri
2019-12-27  2:29       ` Evan Cooch
2019-12-27  7:20         ` Marco Atzeri
2019-12-27 18:20         ` Andrey Repin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f5667cf6-8a2d-c282-a974-be4aca30cb92@gmail.com \
    --to=evan.cooch@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).