Red Hat Bugzilla – Bug 116201
/var/named/chroot/dev/random has wrong minor number
Last modified: 2012-10-05 05:21:10 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.11 (X11; Linux i686; U;) Gecko/20030417
Description of problem:
crw-r--r-- 1 root root 1, 8 Sep 15 14:40 /dev/random
crw-r----- 1 root named 1, 9 Feb 2 13:09
service named start gives syslog message:
named: could not open entropy source /dev/random: permission denied
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.service named start
2.view syslog (might need debug level syslog config)
Adding a new /var/named/chroot/dev/random with minor number 8 (using
mknod) does not get rid of the syslog message at named startup.
/dev/random has the wrong owenership it should be
crw-r----- 1 root named 1, 9 Mar 24 09:46 random
Looks right in bind-9.2.3-9
> /dev/random has the wrong owenership it should be
> crw-r----- 1 root named 1, 9 Mar 24 09:46 random
Surely you don't mean that? Those ownerships and permissions might be
suitable for the __chroot'ed__ dev/random used by named, but not for
Yes I meand /var/named/chroot/dev/random.
Sorry about that.
Apologies for the long delay. I've recently upgraded to Fedora Core 2
(bind-chroot-9.2.3-13), with the following result:
ls -l /var/named/chroot/dev
-rw-r----- 1 root named 0 Mar 25 2003 null
-rw-r----- 1 root named 0 Mar 14 2003 random
Ownerships look reasonable. Permissions might be OK although I would
have expected at least g+w on null.
However, both files are now ordinary files, not devices. Surely that
can't be right?
This was fixed in bind-9.2.4rc6-6 (Latest version bind-9.2.4rc7-10).
(In reply to comment #7)
> This was fixed in bind-9.2.4rc6-6 (Latest version bind-9.2.4rc7-10).
With bind9-9.7.3.df same problem today;
seems solved setting group 'bind' (not worked with 'named')
srw-rw-rw- 1 root root 0 Oct 5 09:09 log
crw-rw---- 1 root root 1, 3 Oct 5 02:21 null
crw-rw---- 1 root bind 1, 8 Oct 5 02:21 random