linux-kernel - Re: ndiswrapper and GPL-only symbols redux

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: <20080129225701.GS8767@does.not.exist>
Date:	Wed, 30 Jan 2008 00:57:01 +0200
From:	Adrian Bunk <bunk@...nel.org>
To:	Pavel Roskin <proski@....org>
Cc:	linux-kernel@...r.kernel.org,
	Jon Masters <jonathan@...masters.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Giridhar Pemmasani <pgiri@...oo.com>, rms@....org
Subject: Re: ndiswrapper and GPL-only symbols redux

On Tue, Jan 29, 2008 at 04:22:45PM -0500, Pavel Roskin wrote:
> Hello!
> 
> It have come to my attention that a patch has been committed to the
> kernel with the explicit purpose of tainting ndiswrapper - the kernel
> module allowing Windows NDIS drivers for Ethernet and Wireless cards to
> be used by the kernel.
>...
> Just to reiterate some points from the old discussion:
>...
> - no copyright violation is involved, as Windows drivers are not derived
> from Linux sources
>...

It is interesting that someone posting with an @gnu.org address claims
that dynamic linking of not GPLv2 compatible code into GPLv2 code was
not a copyright violation.

Is it an official statement of the FSF that such linking is considered 
legal?

(RMS added to Cc)

> Regards,
> Pavel Roskin

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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