[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061023113523.50028.qmail@web32402.mail.mud.yahoo.com>
Date: Mon, 23 Oct 2006 04:35:23 -0700 (PDT)
From: Giridhar Pemmasani <pgiri@...oo.com>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: linux-kernel@...r.kernel.org
Subject: Re: incorrect taint of ndiswrapper
--- Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> However by then it has already dynamically linked with explicit GPLONLY
> symbols so it cannot then load a binary windows driver but should unload
> itself or refuse to load anything but the GPL ndis drivers (of which
> afaik only one exists), and even then they expect an environment
> incompatible with the Linux kernel.
So the idea of tainting is to _prevent_ any binary code being loaded into
kernel, even if kernel is marked as having binary code loaded, which I
thought was the purpose of tainting (so that people not interested in dealing
with binary code know they don't have/want to)? If that is the goal, how do
you know this scheme of adding names to module loader in kernel guarantees
that (now or in future)?
Thanks,
Giri
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists