From: Erik Soderquist <ErikSoderquist@gmail.com>
To: Brian.Inglis@systematicsw.ab.ca, cygwin <cygwin@cygwin.com>
Subject: Re: ssh login to cygwin bash?
Date: Thu, 29 Mar 2018 21:33:00 -0000 [thread overview]
Message-ID: <CACoZoo2BM6Bdbk9TgGQa-vRW4PqOYBkTcwhRB=eX1QfwfATj0Q@mail.gmail.com> (raw)
In-Reply-To: <f362ae86-2914-30b5-eaeb-4fae8598a6db@SystematicSw.ab.ca>
On Thu, Mar 29, 2018 at 4:17 PM, Brian Inglis wrote:
>> I would actually like to know how you managed this, as I have a couple
>> use cases where this is what I do need...
>
> W10 Developer mode installs and enables minimal MS SSH server for Settings
> "Device discovery" mDNS service "SSDP Discovery", also "SSH Server Broker", and
> "SSH Server Proxy" services.
> Enable/disable them to affect MS W10 SSH server.
> In Developer mode you may also have optional Features you can add for OpenSSH
> Server and OpenSSH Client.
>
> W10 SSH can connect to WSL bash: web search for "W10 SSH WSL bash".
That assumes W10 is even an option, and that is not always the case,
especially in legacy-required environments
>> This is what I get on all of my cygwin setups where I've installed
>> sshd. Do you have mintty installed?
>
> Base Cygwin package always installed.
I have come across mintty somehow not installed before, so I ask.
-- Erik
--
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
next prev parent reply other threads:[~2018-03-29 21:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 15:02 Ulli Horlacher
2018-03-29 18:02 ` Erik Soderquist
2018-03-29 20:17 ` Ulli Horlacher
2018-03-29 20:33 ` Marco Atzeri
2018-04-26 14:42 ` Ulli Horlacher
2018-03-29 21:19 ` Brian Inglis
2018-03-29 20:21 ` Brian Inglis
2018-03-29 21:33 ` Erik Soderquist [this message]
2018-03-29 19:35 ` 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='CACoZoo2BM6Bdbk9TgGQa-vRW4PqOYBkTcwhRB=eX1QfwfATj0Q@mail.gmail.com' \
--to=eriksoderquist@gmail.com \
--cc=Brian.Inglis@systematicsw.ab.ca \
--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).