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: <1161600064.19388.14.camel@localhost.localdomain>
Date:	Mon, 23 Oct 2006 11:41:04 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Giridhar Pemmasani <pgiri@...oo.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: incorrect taint of ndiswrapper

Ar Sul, 2006-10-22 am 22:41 -0700, ysgrifennodd Giridhar Pemmasani:
> Note that when a driver is loaded, ndiswrapper does taint the kernel (to be
> more accurate, it should check if the driver being loaded is GPL or not, but
> that is not done).

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.


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