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: Fri, 29 Apr 2005 16:30:20 -0700
First 0.97e is an extremely old version of openssh or you are confusing
it with openssl. Current openssh versions are in the 3.9 - 4.0 range.

Secondly when you run the unstable branch of a distribution you risk
this type of behavior, since you are in essence the beta tester. This
would apply to branches such as debian unstable, fedora and gentoo
unstable.

I dont see any bugs related to this on bugs.debian.org and that is who
you should be talking with since every distirbution has thier own set of
home grown patches most of the packages they maintain and sometimes they
dont play well together.  

On Fri, 2005-04-29 at 07:56 +0100, Peter Childs wrote:
    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
 

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