2 thoughts on - Ssh Issues With CentOS 6

• …on what? A 64 MiB bargain basement VPS, an enterprise grade 32 GiB server, a reflashed network switch…?

  Why is that relevant? That message likely contains less than 1 kiB of ASCII text, and isn’t held in RAM continuously anyway.

  That feature is so unimportant with respect to memory usage that it was added to Unix back in the days when 1 kiB of RAM cost real money.

  Specifically what problems? How did you diagnose it, and why do you believe your solution is useful?

  That’s essentially bogus. If /dev/random is blocking due to insufficient entropy, feeding false entropy in from urandom buys you nothing, other than to fool /dev/random into thinking it has more entropy than it actually does.

  On a typical Linux system, /dev/random and /dev/urandom get their entropy from the same source, so feeding pseudorandom numbers from one to the other is essentially lying to the kernel; it will get its revenge on you for that lie, eventually.

  rngd is only useful when reading from a [P]RNG that the kernel isn’t already using for entropy, such as a hardware RNG.

  Why would it? The kernel PRNG’s entropy pool has nothing to do with free RAM.

  Why is the message truncated? That sounds like memory *corruption* to me, rather than memory exhaustion.

  Are you seeing activity by the OOM killer?

  http://www.linuxdevcenter.com/pub/a/linux/2006/11/30/linux-out-of-memory.html

  Are you dealing with software you wrote yourself, or only software that came with CentOS? If the former, have you run it under valgrind?

• Indeed, the correct solution is to use /dev/urandom instead of /dev/random.

  http://www.2uo.de/myths-about-urandom/