Grrr... modprobe.conf

Adam Williamson awilliam at redhat.com
Mon Sep 20 12:49:30 UTC 2010


On Mon, 2010-09-20 at 08:35 -0400, Tom Horsley wrote:
> On Sun, 19 Sep 2010 09:08:43 -0400
> Tom Horsley wrote:
> 
> > After all these years, something from the fedora repos
> > (the only ones I have active in my F14 partition) is still
> > creating an (empty) /etc/modprobe.conf file.
> 
> Well, I found something with a grep -r of the whole
> f14 partition :-).
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=635640
> 
> Don't know if dracut is really the source of the file
> though.

So, if this bug is valid as described it's a significant security issue.
However, I'm not sure it's simple. I've just checked, and none of my F14
test spins (basically RC2) have a modprobe.conf booted live. The clean
installed system from the desktop live image that I have in my test VM
currently doesn't have one either. Neither does my 'work' system itself.

If it's dracut as you surmise, it may perhaps happen only on installing
a kernel after initial install. I guess also it may only happen when
installing from non-live media. We should definitely look into this
urgently.

What's the last-touched date of your /etc/modprobe.conf ? Do you know
when that is in relation to the lifetime of the install?
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net



More information about the test mailing list