public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: sshd refuses connections since upgrade to 2.4.0-1
Date: Fri, 29 Jan 2016 12:56:00 -0000	[thread overview]
Message-ID: <20160129114445.GA14874@calimero.vinschen.de> (raw)
In-Reply-To: <trinity-931878d8-4e31-4c79-b1b1-d034981445fc-1454007393135@3capp-gmx-bs40>

[-- Attachment #1: Type: text/plain, Size: 2301 bytes --]

On Jan 28 19:56, prs_cygwin@quantentunnel.de wrote:
> Hi!
> 
> Long time Cygwin user but first time error reporter to this mailing list.
> Since upgrading my 32-bit Cygwin installation on Win7SP1 x64 from
> 2.3.1-1 to the current 2.4.0-1 (and also 2.5.0-0.1 in my despair) I
> can't connect to sshd running as a service anymore.
> The service starts and spawns a child in order to handle the
> connection request, but that fails even when connecting from
> localhost.
> I triaged the problem by trying snapshots between the two releases and
> traced it to a change after 20151129:
> cygwin1-20151129.dll works
> cygwin1-20151203.dll fails
> 
> The sshd.log remains empty.
> In order to create more information to go on I ran strace on the
> parent (cyg_server spawned) sshd and tried to connect, the strace-log
> (sshd_cygwin2.4.0_20160109) is attached together with a slightly
> redacted cygcheck.out
> 
> Thanks for looking into this!
> 
> P.S. As can be seen from the strace I'm running Agnitum Outpost
> Firewall Pro and the current EMET - both has never been a problem with
> Cygwin's sshd (in this installation since May 2010).

An "Access denied" error occurs, apparently in a Windows DLL while
loading Windows DLLs.  It's hard to tell what the reason is, but what
strikes me as weird is that the crash occurs right after this Agnitum
thingy has been injected into the process:

--- Process 17828 loaded C:\PROGRA~1\Agnitum\OUTPOS~1\wl_hook.dll at 10000000
--- Process 17828 unloaded DLL at 10000000
--- Process 17828 loaded C:\PROGRA~1\Agnitum\OUTPOS~1\wl_hook.dll at 01280000
--- Process 17828 loaded C:\Windows\SysWOW64\shell32.dll at 762F0000
--- Process 17828 loaded C:\Windows\SysWOW64\shlwapi.dll at 75DE0000
--- Process 17828 thread 18284 exited with status 0xc0000022
--- Process 17828 thread 18412 exited with status 0xc0000022
--- Process 17828 thread 17624 exited with status 0xc0000022
--- Process 17828 exited with status 0xc0000022
154769 11583429 [waitproc] sshd 8404 pinfo::status_exit: *** STATUS_0xC0000022

Did you try excluding sshd from the checks of that scanner?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-01-29 11:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-28 20:18 prs_cygwin
2016-01-29 12:56 ` Corinna Vinschen [this message]
2016-01-29 18:41 Patrick Schmitt
2016-01-30  3:21 ` Achim Gratz

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=20160129114445.GA14874@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.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).