Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

setreuid failed (was: SSH daemon doesn't accept incoming connections)

from [Kirill Kuvaldin] Network Security [Permanent Link]
Subject: setreuid failed (was: SSH daemon doesn't accept incoming connections)
Date: Sun, 20 May 2007 11:36:05 +0400 
There is a description of the problem I have stumbled across a while ago:
http://lists.debian.org/debian-user/2007/05/msg02019.html
Basically, I wasn't able to establish the SSH connection even to localhost.

I've finally figured out what had caused the problem. I ran sshd in
debug mode and noticed
"setreuid 100: Resource temporarily unavailable". The sshd user id is
100 in debian.
It turned out that the setreuid(2) syscall has been failing for some reason.

I wrote a simple test program (http://epsmu.com/~kuvkir/setreuid.c) to
check that
and it appeared that setreuid is failing for this particular uid (100).
I'm not sure if it is a debian or an openssh specific issue,
but rather glibc (2.3.6-ds1-13) or maybe kernel (2.6.18-4-powerpc
debian) related
thing.

For now I has changed the sshd uid to another value and restared the ssh daemon
and it works fine now.

Thanks,
Kirill

[More messages with this same subject...]




<Prev in Thread] Current Thread [Next in Thread>
  • setreuid failed (was: SSH daemon doesn't accept incoming connections), Kirill Kuvaldin <=
Previous by Date:  Re: graceful ssh key management, Kevin Hunter
Next by Date:  using ssh authentication with sudo, Eric S. Johansson
Previous by Thread:  logging, Oliver Block
Next by Thread:  using ssh authentication with sudo, Eric S. Johansson
Indexes:  [Date] [Thread] [Top] [All Lists]