From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: after ssh connection is getting closed
Date: Wed, 09 Feb 2011 10:37:00 -0000 [thread overview]
Message-ID: <20110209103731.GA16194@calimero.vinschen.de> (raw)
In-Reply-To: <4A2CF3C24E05B348A46BAF5A7C4593D40F8E9001@BTCMVEXC1-PRD.hq.netapp.com>
On Feb 9 12:14, Sarkar, Kaushik wrote:
> After connecting through ssh immediately my connection is getting
> closed.
I can't reproduce this problem, neither with Cygwin 1.7.7, nor with the
latest Cygwin from CVS, neither with OpenSSH 5.6, nor 5.7, nor 5.8.
However, I *could* reproduce it on my machine when trying to login using
another account than my own. After some digging it turned out that one
of my DLLs in /bin had 700 permissions, rather than the correct 755
permissions. That was a result of some debugging I did a couple of days
back. Anyway, after fixing that, the login worked fine. Just calling
`chmod 755 /bin/*.dll' did the trick.
Here's another potential cause: Right now there appears to be a problem
with the latest bash (see the mailing list archives of the last few
days), but for some unknown reason the problem doesn't manifest on all
machines.
I assume you didn't only update cygwin or openssh, but all packages.
Restart setup and revert bash to the older 3.2.51-24 and see if it fixes
your problem. Or, set the login shell of the account you're trying
to login to to /bin/dash, or /bin/tcsh, or any other non-bash shell
available.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
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:[~2011-02-09 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 6:44 Sarkar, Kaushik
2011-02-09 10:37 ` Corinna Vinschen [this message]
2011-02-09 6:46 Sarkar, Kaushik
2011-02-09 16:03 ` Larry Hall (Cygwin)
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=20110209103731.GA16194@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).