Mailing List Archive

[Bug 664] sshd refuses to accept connections, fails with setreuid 75: Operation not permitted error
http://bugzilla.mindrot.org/show_bug.cgi?id=664

Summary: sshd refuses to accept connections, fails with setreuid
75: Operation not permitted error
Product: Portable OpenSSH
Version: 3.7.1p1
Platform: PPC
OS/Version: Mac OS X
Status: NEW
Severity: major
Priority: P2
Component: sshd
AssignedTo: openssh-bugs@mindrot.org
ReportedBy: openssh.9.aktnist@antichef.com


MacOS 10.2.6, installing to fix vulnerability in default install

Using openssl 0.9.6i from fink

Installation appears to work, but trying to connect from remote host (with
server running in sshd -de mode) gives following (short) debug trace:

{snip}
Server listening on 0.0.0.0 port 22.
Generating 768 bit RSA key.
RSA key generation complete.
debug1: Server will not fork when running in debugging mode.
Connection from 129.6.120.31 port 28571
debug1: Client protocol version 2.0; client software version OpenSSH_3.4p1
debug1: match: OpenSSH_3.4p1 pat OpenSSH_3.2*,OpenSSH_3.3*,OpenSSH_3.4*,OpenSSH_3.5*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-1.99-OpenSSH_3.7.1p1
debug1: permanently_set_uid: 75/75
setreuid 75: Operation not permitted
debug1: Calling cleanup 0x24ad8(0x0)

Tried enabling BROKEN_SETREUID in config.h, still failed with

setuid 75: Operation not permitted

Thanks!



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 664] sshd refuses to accept connections, fails with setreuid 75: Operation not permitted error [ In reply to ]
http://bugzilla.mindrot.org/show_bug.cgi?id=664

openssh.9.aktnist@antichef.com changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE



------- Additional Comments From openssh.9.aktnist@antichef.com 2003-09-18 07:03 -------


*** This bug has been marked as a duplicate of 665 ***



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.