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: netstat from ssh_prng_cmds taking too much CPU on AIX

Subject: Re: netstat from ssh_prng_cmds taking too much CPU on AIX
Date: Sun, 20 Mar 2005 15:52:20 +1100
Ronald B. Miller wrote:
I recently installed OpenSSH 3.9p1 on an AIX 5.1 system. Since then we have
noticed that ssh_rand_helper has started netstat commands (from
ssh_prng_cmds) that don't finish quickly and cause the CPU to jump to almost
no idle for extended lengths of time - usually about 20 minutes or so.

Which variants of the netstat command are causing the problem? You can run ssh-rand-helper -vvv on its own and watch its progress.


If there are processes hanging around after ssh-rand-helper times them out it means they're ignoring a SIGINT, so either it's being deliberately caught or (more likely) the command is stuck in a syscall.

I have commented out the netstat commands in the ...cmds file and wonder if
anyone has either a warning about doing that or a better resolution to my
problem. Thanks in advance.

The best long-term solution is to use prngd instead of the built-in entropy gatherer.


--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

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