From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: cygwin 3.0.1-1 breaks my sshd install
Date: Wed, 20 Feb 2019 20:25:00 -0000 [thread overview]
Message-ID: <47883ab06634fed3ecdaa375016dc3fb@smtp-cloud8.xs4all.net> (raw)
In-Reply-To: <alpine.DEB.2.21.1902201038580.32163@ckhb05>
On Wed, 20 Feb 2019 10:53:09, scowles at ckhb dot org wrote:
>
> i can confirm the same behaviours on a 3.0.0 system. i've done several checks
> and have been unable to find the source of the problem. ssh -vvv shows that the
> connection proceeds all the way through the connection process, sends the
> appropriate key tokens, then the server abruptly closes the connection. all
> accounts on the system show the same results.
>
> my 2.11.1 system, with identical ssh[d]_config files has no such problems.
>
> on both systems, all relevant files and directories have correct owners and
> permissions.
Yes, failure for 3.0.0 (and 3.0.1); success for 2.11.2
Henri
64-@@ uname -a
CYGWIN_NT-6.1 Seven 3.0.1(0.338/5/3) 2019-02-20 10:19 x86_64 Cygwin
64-@@ tail /var/log/sshd.log
Server listening on 0.0.0.0 port 222.
seteuid 1004: Permission denied
=====
--
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:[~2019-02-20 20:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19759126.568100.1550686604174.ref@mail.yahoo.com>
2019-02-20 18:53 ` James R. Phillips via cygwin
2019-02-20 19:04 ` scowles
2019-02-20 19:47 ` Bill Stewart
2019-02-20 20:01 ` scowles
2019-02-20 20:25 ` Houder [this message]
2019-02-20 21:27 ` Corinna Vinschen
2019-02-20 21:34 ` Andy Moreton
2019-02-20 21:39 ` Corinna Vinschen
2019-02-20 22:13 ` scowles
2019-02-20 21:50 ` Houder
2019-02-20 22:38 ` Corinna Vinschen
2019-02-20 22:44 ` Corinna Vinschen
2019-02-21 11:43 ` Corinna Vinschen
2019-02-21 16:01 ` Houder
2019-02-23 19:15 ` Cary Lewis
2019-02-24 6:58 ` Cary Lewis
2019-09-15 6:45 ` Basin Ilya
2019-09-15 7:07 ` Basin Ilya
2019-02-20 21:35 ` Bill Stewart
2019-02-20 21:37 ` Houder
2019-02-20 21:50 ` Corinna Vinschen
2019-02-20 22:08 ` Houder
2019-02-20 22:32 ` Houder
2019-02-20 22:43 ` Corinna Vinschen
2019-02-21 5:16 ` Houder
2019-02-20 22:36 ` scowles
2019-02-20 23:08 ` Corinna Vinschen
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=47883ab06634fed3ecdaa375016dc3fb@smtp-cloud8.xs4all.net \
--to=houder@xs4all.nl \
--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).