public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Erik Soderquist <erik.soderquist@gmail.com>
To: cygwin <cygwin@cygwin.com>
Subject: Cygwin sshd vs Microsoft sshd
Date: Fri, 05 Oct 2018 20:35:00 -0000	[thread overview]
Message-ID: <CACoZoo0tyqH4Vjsm4wpSTau7LjhPv5rdj5UhK3R77CcS+fbN0g@mail.gmail.com> (raw)

referencing threads
https://sourceware.org/ml/cygwin/2018-06/msg00249.html
https://sourceware.org/ml/cygwin/2018-07/msg00171.html

Microsoft's 1803 update for Windows 10 breaks and/or interferes with
the normal operation of Cygwin's sshd

On one of my work-provided laptops, I will be required to update to
the 1803 build within the next few weeks, and currently have Cygwin
sshd configure and working.  With the advance warning, what doc should
I collect before the update is applied to better diagnose the root
cause since this seems to be inconsistent?  While I certainly would be
thrilled if I did not have the issue others have experienced, I'm not
holding my breath either, and see this as an opportunity to get
"before" doc for comparison to "after" doc should any of the problems
manifest in my environment.

-- Erik

--
"I do not think any of us are truly sane, Caleb. Not even you. Courage
is not sanity. Being willing to die for someone else is not sanity."
... "Love is not sane, nor is faith." ... "If sanity lacks those
things, Caleb, I want no part of it."

-- Alexandria Terri in "Weaving the Wyvern" by Alexis Desiree Thorne

--
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:[~2018-10-05 20:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CACoZoo0tyqH4Vjsm4wpSTau7LjhPv5rdj5UhK3R77CcS+fbN0g@mail.gmail.com \
    --to=erik.soderquist@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).