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]

Re: ssh going zombie

Subject: Re: ssh going zombie
Date: Wed, 04 May 2005 20:59:06 +0100
Robert L Sowders wrote:

on the server kill the ssh server then restart it with the -d flag to put it into debug mode. This process will not fork and will write all debug output to the stderr (the window you started it from), then connect with winscp and try to duplicate the error you reported.

it should give you some clues as to what is happening.

rls





Peter Childs <dp@expressnationalcarriers.co.uk>
04/28/2005 08:56 PM


To: secureshell@securityfocus.com
cc: Subject: ssh going zombie



Using sshd under Debian Unstable Openssh 0.9.7e

When winscp disconnects from our server the scp process goes zombie and the ssh process hogs the processor on the server. This only seams to happern with winscp and not with scp or ssh under linux. If the subprocess is removed from the sshd config file the a sub sshd process goes zombie instead and the calling sshd process hogs the processor.

I'm think it may have somthing to do with the way winscp talks to sshd , but the winscp people seam to think this is a problem with sshd. I get this feeling this is going to be a problem nobody has a clue on and wishes to blame the other party.


Peter Childs







Ok after installing ssh 4.0 from source I've fixed the problem. It seams that 3.8 which is on debian sarge has a bug when it uses sftp-server in that it does not wait for the process to end and then hogs the processor.

Peter CHilds

<Prev in Thread] Current Thread [Next in Thread>