linux-kernel - Re: [PATCH ??] 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: <45429240.1080800@gmail.com>
Date:	Fri, 27 Oct 2006 19:12:00 -0400
From:	Florin Malita <fmalita@...il.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Andrew Morton <akpm@...l.org>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org, proski@....org, cate@...ian.org,
	gianluca@...networks.biz
Subject: Re: [PATCH ??] Re: incorrect taint of ndiswrapper

Alan Cox wrote:
> Ar Gwe, 2006-10-27 am 18:56 -0400, ysgrifennodd Florin Malita:
>   
>> Also, since driverloader is not GPL-compatible (MODULE_LICENSE("see
>> LICENSE file; Copyright (c)2003-2004 Linuxant inc.")), that check is
>> redundant. How about removing it (applies on top of Randy's patch)?
>>
>>
>> Signed-off-by: Florin Malita <fmalita@...il.com>
>>     
>
> NAK
>
> Older versions of Linuxant's driverloader claim GPL\0some other text and
> systematically set out to abuse the license tag code. We should continue
> to carry the code for this.
>   

Older versions of driverloader won't even build for recent kernels
(actually even the latest - 2.34 - fails with 2.6.19-rc3). Do you know
of any driverloader version that actually works with 2.6.18+ and
misrepresents its license? Seems to me they gave up that practice and
currently the check is useless but if you want to keep it as a statement
I can understand that :)

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