public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: SSHD error child_info_fork
Date: Sun, 06 May 2018 13:39:00 -0000	[thread overview]
Message-ID: <3a16c7bf-e33e-25fa-2ce3-f0546acb0700@gmail.com> (raw)
In-Reply-To: <CAELo-Y2ny4Xh2JLp0cmYzY-eGuWobFK+O_ASYhGndWCiY=yF2w@mail.gmail.com>

On 5/6/2018 3:35 PM, Tasslehoff Burrfoot wrote:
> Hi, I recently noticed a problem with sshd on one of my Windows 10 updated
> to the recent 1803 update.
> First of all I'm using cygwin x86 updated to the latest packages, during
> sshd startup I have no errors in the Windows Event Log using services.msc
> or using "cygrunsrv --start sshd", same launching sshd deamon from console.
> I have no firewall blocking connections and the ssh client is connecting
> from a debian host on lan on the same subnet (no networking issues).

If you have a 64bit system you should use the x86_64 bit version


> debug1: match: OpenSSH_6.7p1 Debian-5+deb8u4 pat OpenSSH* compat 0x04000000
> debug1: Local version string SSH-2.0-OpenSSH_7.7
>        0 [main] sshd 11752 child_info_fork::abort:
> C:\cygwin\bin\cygiconv-2.dll: Loaded to different address: parent(0x850000)
> != child(0xED0000)
> fork of unprivileged child failed
> debug1: do_cleanup
> =====================
> 
> Do you have any suggestion?
> 
> Thanks
> 
> Tas



as mentioned here
> Problem reports:       http://cygwin.com/problems.html

please provide the cygcheck.out

--
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-05-06 13:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-06 13:35 Tasslehoff Burrfoot
2018-05-06 13:39 ` Marco Atzeri [this message]

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=3a16c7bf-e33e-25fa-2ce3-f0546acb0700@gmail.com \
    --to=marco.atzeri@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).