recent NAMED update has an entropy problem
Tim
ignored_mailbox at yahoo.com.au
Fri Dec 23 18:49:31 UTC 2005
Amongst my logwatch information, I see the following sort of thing
reported all the time, after the recent NAMED update:
using pre-chroot entropy source /dev/random: 2 Time(s)
Does anyone else see the same thing?
I see this on two updated boxes (one which gets frequently rebooted,
another which rarely does), but not on a box that was left un-updated.
For what it's worth, here's the output from listing the containing
directories:
ls -l /var/named/chroot/
total 24
drwxr-xr-- 2 root named 4096 Oct 20 07:45 dev
drwxr-x--- 2 root named 4096 Dec 20 16:15 etc
dr-xr-xr-x 120 root root 0 Dec 23 00:35 proc
drwxr-x--- 5 root named 4096 Mar 14 2003 var
ls -l /var/named/chroot/dev/
total 12
crw-r--r-- 1 root root 1, 3 Sep 23 16:25 null
crw-r--r-- 1 root root 1, 8 Sep 23 16:25 random
crw-r--r-- 1 root root 1, 5 Sep 23 16:25 zero
And some other parent directory permissions:
drwxr-x--- 5 root named 4096 Dec 20 16:15 /var/named/
drwxr-x--- 6 root named 4096 Oct 20 07:45 /var/named/chroot/
--
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
More information about the users
mailing list