linux-kernel - Re: incorrect taint of ndiswrapper

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1161692533.22348.19.camel@localhost.localdomain>
Date:	Tue, 24 Oct 2006 13:22:13 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	Randy Dunlap <rdunlap@...otime.net>,
	Giridhar Pemmasani <pgiri@...oo.com>,
	linux-kernel@...r.kernel.org
Subject: Re: incorrect taint of ndiswrapper

Ar Maw, 2006-10-24 am 15:12 +0300, ysgrifennodd Pekka Enberg:
> On 10/24/06, Randy Dunlap <rdunlap@...otime.net> wrote:
> > The kernel should not depend on a not-in-tree kernel module to
> > taint the kernel.  The kernel can and should do that itself.
> 
> Agreed. But should the kernel disallow the use of _GPL symbols for
> ndiswrapper? I would say no.

I'd agree providing the attempt to taint function allows an error return
if it did so and it then refuses to load non-GPL windows drivers.

-
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/