Bug 285 - 3.3p1 on Linux 2.2.x doesn't accept connections
Summary: 3.3p1 on Linux 2.2.x doesn't accept connections
Status: CLOSED FIXED
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: sshd (show other bugs)
Version: -current
Hardware: ix86 Linux
: P1 normal
Assignee: OpenSSH Bugzilla mailing list
URL:
Keywords:
: 286 288 289 292 293 299 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-06-23 19:32 AEST by Vid Strpic
Modified: 2004-04-14 12:24 AEST (History)
7 users (show)

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 Vid Strpic 2002-06-23 19:32:14 AEST 
Jun 22 22:47:29 *server* sshd[711]: fatal: mmap(65536): Invalid argument

And it closes the connection. Tested on two systems, both kernel 2.2.21, on 
other two systems with kernel 2.4.18 sshd works perfectly, and I'm able to 
login.
Comment 1 Darren Tucker 2002-06-23 20:31:34 AEST 
Disabling PrivSep (add "UsePrivilegeSeparation no" to sshd_config) should get it 
working on 2.2 kernels.

3.3p1 defaults PrivSep to on. Previous releases (that supported it) defaulted to 
off.
Comment 2 Ben Lindstrom 2002-06-24 03:27:58 AEST 
The issue is mmap() on Linux 2.2 kernel does not support any of the useful 
options in order to allow PrivSep and Compression at the same time.

Either disable privsep (like what dtucker@ said) or change 'Compression yes' 
to 'Compression no'.

There is a patch being worked out to straight some of this out.
Comment 3 Ben Lindstrom 2002-06-24 03:40:29 AEST 
*** Bug 286 has been marked as a duplicate of this bug. ***
Comment 4 Greg Jewell 2002-06-25 03:16:47 AEST 
OpenServer 5.0.x also rejects incoming connections.  The user will be prompted 
for their password, but the connection will close immediately after.  The fixes 
suggested (setting "UsePrivilegeSeparation" and/or "Compression" to "no") 
resolve the inability to connect, though.
Comment 5 Ben Lindstrom 2002-06-25 09:21:09 AEST 
*** Bug 288 has been marked as a duplicate of this bug. ***
Comment 6 Darren Tucker 2002-06-25 17:08:43 AEST 
*** Bug 289 has been marked as a duplicate of this bug. ***
Comment 7 Darren Tucker 2002-06-25 20:22:29 AEST 
*** Bug 292 has been marked as a duplicate of this bug. ***
Comment 8 Darren Tucker 2002-06-25 23:36:15 AEST 
*** Bug 293 has been marked as a duplicate of this bug. ***
Comment 9 Jim Cooper 2002-06-26 03:29:08 AEST 
bug also found on Kernel 2.2.17-14 installed in Cartman Redhat 6.1
not seen on Mac OS X 10.1.5
"Compression no" solves on Linux
Comment 10 John Anderson 2002-06-26 06:46:14 AEST 
Also found on Kernel 2.2.14-5.0 Red Hat 6.2 (Zoot).

I can't make Compression no work.  With UsePrivilegeSeparation No, it doesn't 
work either.
Comment 11 Darren Tucker 2002-06-26 22:03:48 AEST 
*** Bug 299 has been marked as a duplicate of this bug. ***
Comment 12 Ambrose Li 2002-06-28 02:06:24 AEST 
If neither "Compression no" nor "UsePrivilegeSeparation no" work, are your host
keys in ssh1 format? It seems that the new ssh's doesn't understand ssh1 format
host keys. If you use ssh2-format rsa/dsa keys, does it work?
Comment 13 John Anderson 2002-06-28 22:59:08 AEST 
OpenSSH 3.4p1 fixed this problem.
Kernel 2.2.14-5.0 - Compression yes and UsePrivilegeSeparation yes work
Kernel 2.2.12-32 - Compression musr be disabled for UsePrivilegeSeparation to 
work.

I wanted to pass that along, I didn't know if that was "known" or not.
Comment 14 Damien Miller 2004-04-14 12:24:18 AEST 
Mass change of RESOLVED bugs to CLOSED