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: <1161817118.7615.34.camel@localhost.localdomain>
Date:	Wed, 25 Oct 2006 23:58:38 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	David Weinehall <tao@....umu.se>
Cc:	Pavel Roskin <proski@....org>, linux-kernel@...r.kernel.org
Subject: Re: incorrect taint of ndiswrapper

Ar Mer, 2006-10-25 am 23:33 +0200, ysgrifennodd David Weinehall:
> Personally I feel that no matter if they are legal or not, we should not
> cater to such drivers in the first place.  If it's trickier to use
> Windows API-drivers under Linux than to write a native Linux driver,
> big deal...  We don't want Windows-drivers.  We want native drivers.

Neither taint nor _GPL are intended to stop people doing things that, in
the eyes of the masses, are stupid. The taint mark is there to ensure
that they don't harm the rest of us. The FSF view of freedom is freedom
to modify not freedom to modify in a manner approved by some defining
body.

Alan

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