Bug 3028 - The named init script uses the wrong minor for /var/lib/named/dev/urandom
Summary: The named init script uses the wrong minor for /var/lib/named/dev/urandom
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2011-10-13 01:56 CEST by Dave Hodgins
Modified: 2012-03-10 14:57 CET (History)
3 users (show)

See Also:
Source RPM: bind-9.8.0-6.P4.mga1.src.rpm
CVE:
Status comment:

Attachments
Patch to fix /etc/rc.d/init.d/named (663 bytes, patch)
2011-10-13 01:57 CEST, Dave Hodgins 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Description Dave Hodgins 2011-10-13 01:56:25 CEST 
On startup, /etc/rc.d/init.d/named creates /var/lib/named/dev/urandom
with a minor of 8.  It should be 9 as per "man 4 random"

This will make /var/lib/named/dev/urandom act like /dev/random, potentially
causing named to stop until more random data becomes available.

Thanks to the poster Aragorn in the usenet group alt.os.linux.mandriva for
noticing this.
Comment 1 Dave Hodgins 2011-10-13 01:57:27 CEST 
Created attachment 949 [details]
Patch to fix /etc/rc.d/init.d/named
Comment 2 Marja Van Waes 2011-12-09 20:44:26 CET 
no maintainer for bind

@ guillomovitch

Can you have a look at this, please?

Keywords: (none) => PATCH
CC: (none) => guillomovitch, marja11

Comment 3 Marja Van Waes 2012-01-29 11:31:54 CET 
@ anssi

did bind-9.8.1P1-1.1.mga1 fix this, too?
If it did I look over it.

CC: (none) => anssi.hannula

Comment 4 Anssi Hannula 2012-01-29 14:38:31 CET 
Nope.
Comment 5 Guillaume Rousse 2012-03-08 20:02:00 CET 
Fixed in incoming 9.9.0-3mga2.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 6 Dave Hodgins 2012-03-08 22:59:14 CET 
Will it be fixed for Mageia 1?
Comment 7 Marja Van Waes 2012-03-10 08:34:27 CET 
(In reply to comment #6)
> Will it be fixed for Mageia 1?

reopening, because this report is against Mageia 1

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 8 Dave Hodgins 2012-03-10 09:10:35 CET 
Also, as noted in Bug 4822 my patch only fixes the minor node for
new installations.  Either the patch needs to be changed to have
the script delete and recreate the node, or it should be done in
a scriptlet, if that can be made to work.
Comment 9 Guillaume Rousse 2012-03-10 14:57:05 CET 
I don't think this problem is serious enough to justify an update for mageia 1, at least for me. If someone wants to do the work, tough, the fix is in current cauldron package.

Status: REOPENED => RESOLVED
Resolution: (none) => WONTFIX
Note You need to log in before you can comment on or make changes to this bug.