Bug 923 - Connection closed after autentication
Summary: Connection closed after autentication
Status: CLOSED INVALID
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: sshd (show other bugs)
Version: -current
Hardware: ix86 Cygwin on NT/2k/Win7-11
: P2 critical
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-02 11:32 AEST by akira
Modified: 2006-10-07 11:37 AEST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description akira 2004-09-02 11:32:21 AEST 
The 3.9p1 version of the sshd server for cygwin can't be accessed from any
computer or localhost. It closes the session with a "connection closed" message
and a 255 Exit code after the user is autenticated. It occurs with both password
and ssh keys. Tested with different computers with the same result and as I read
on "tech.erdelynet.com" forums I am not the only one with the same problem.

  This is not happening if the latest 3.8 version is installed instead 3.9p1. It
works completely OK in that case. The problem is only encountered with 3.9p1
version.
Comment 1 Darren Tucker 2004-09-02 14:42:46 AEST 
The combination of UsePrivilegeSeparation (on by default) + reexec (also on by
default) apparently tickles a bug in Cygwin itself.

According to Corinna there are 3 ways to workaround that problem:

- Either switch off PrivSep,
- or use the -r option to switch off reexec'ing,
- or use one of the latest Cygwin developer snapshot from
  http://www.cygwin.com/snapshots/
  The bug should be solved since the 2004-Aug-19 snapshot.
Comment 2 Darren Tucker 2004-09-11 15:04:47 AEST 
Since this is not actually a bug with OpenSSH, I'm closing this.  Please re-open
if you can reproduce with the updated cygwin DLL.
Comment 3 Darren Tucker 2006-10-07 11:37:00 AEST 
Change all RESOLVED bug to CLOSED with the exception of the ones fixed post-4.4.