Bug 293 - sshd 3.3p1 doesn't work on Slackware
Summary: sshd 3.3p1 doesn't work on Slackware
Status: CLOSED DUPLICATE of bug 285
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: sshd (show other bugs)
Version: -current
Hardware: ix86 Linux
: P2 critical
Assignee: OpenSSH Bugzilla mailing list
URL: http://www.slynet.lu/
Keywords:
Depends on:
Blocks:
 
Reported: 2002-06-25 23:13 AEST by Slyoldfox
Modified: 2004-04-14 12:24 AEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Slyoldfox 2002-06-25 23:13:42 AEST
After compiling sshd 3.3p1 on Slackware 7.2 and Slackware 8.0
(for Slackware 7.2 with:
LIBS=-lcrypt ./configure --with-ssl-dir=/usr/local/openssl-0.9.6d --with-tcp-
wrappers
)

the sshd doesn't allow new connections even tho 3.2.3p1 does.
The error i get in /var/log/syslog is:
--
Jun 25 11:27:14 Slynet sshd[18678]: fatal: mmap(65536): Invalid argument
Jun 25 11:27:48 Slynet sshd[18682]: fatal: mmap(65536): Invalid argument
Jun 25 11:30:31 Slynet sshd[18733]: fatal: mmap(65536): Invalid argument
Jun 25 11:53:03 Slynet sshd[24948]: fatal: mmap(65536): Invalid argument
Jun 25 11:53:25 Slynet sshd[24950]: fatal: mmap(65536): Invalid argument
Jun 25 11:54:38 Slynet sshd[24954]: fatal: mmap(65536): Invalid argument
Jun 25 12:22:40 Slynet sshd[31001]: fatal: mmap(65536): Invalid argument
--

This happens for every incoming connection .. the connection brakes off and the 
other client closes with a 'broken pipe'
Comment 1 Darren Tucker 2002-06-25 23:36:12 AEST

*** This bug has been marked as a duplicate of 285 ***
Comment 2 Damien Miller 2004-04-14 12:24:18 AEST
Mass change of RESOLVED bugs to CLOSED